Fix ambigity on ObjInstance#toString() #94

New Issue

sergeych · 2025-12-22T02:46:13+03:00

sergeych commented

2025-12-22 02:46:13 +03:00

when toString() is implemented in lyng, when called from kotlin toString(scope) usually calls builtin version, not the overridden one, but Lyng toString() calls ir properly, it causes bugs in expression like "result: "+value if value is an Lyng user class with implemented toString(); right now "result: "+value.toString() only works, which is ugly.

when toString() is implemented in lyng, when called from kotlin toString(scope) usually calls builtin version, not the overridden one, but Lyng toString() calls ir properly, it causes bugs in expression like `"result: "+value` if value is an Lyng user class with implemented toString(); right now `"result: "+value.toString()` only works, which is ugly.

sergeych added the

Kind/Bug

label 2025-12-22 02:46:13 +03:00

sergeych referenced this issue from a commit

2025-12-22 07:32:30 +03:00

fix #94 overridden toString() now is called correctly in known cases, default implementation is still generated for ObjInstances and some other classes

sergeych closed this issue

2025-12-22 07:32:30 +03:00

Sign in to join this conversation.