You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current implementation of the initializer functions, data types are unconditionally initialized with their declared type-initializer. If a new initializer is set for an instance, it is currently not initialized correctly.
We should adapt the implementation to allow non-default-initializers in init-functions (fb: foo := (s1 := REF(ps)); such that __init_foo initializes foo.s1 with the address of ps instead of the default type initializer).
The text was updated successfully, but these errors were encountered:
In the current implementation of the initializer functions, data types are unconditionally initialized with their declared type-initializer. If a new initializer is set for an instance, it is currently not initialized correctly.
We should adapt the implementation to allow non-default-initializers in init-functions (
fb: foo := (s1 := REF(ps));
such that__init_foo
initializesfoo.s1
with the address ofps
instead of the default type initializer).The text was updated successfully, but these errors were encountered: