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 some cases, registered types should have generated getters but not setters, e.g.:
structfoo {
MyStructdata[1];
};
If you register-type foo [data MyStruct] you'll get an error during compilation, since it generates a setter for data and MyStruct[1] is not an assignable type. However, getters are still valid.
Perhaps we could permit an optional form in the registration, that, when present, restricts the generated functions:
(register-type foo [(data [getter]) MyStruct])
When omitted, we just use the default behavior and generate all the getters/setters.
The text was updated successfully, but these errors were encountered:
In some cases, registered types should have generated getters but not setters, e.g.:
If you
register-type foo [data MyStruct]
you'll get an error during compilation, since it generates a setter fordata
andMyStruct[1]
is not an assignable type. However, getters are still valid.Perhaps we could permit an optional form in the registration, that, when present, restricts the generated functions:
When omitted, we just use the default behavior and generate all the getters/setters.
The text was updated successfully, but these errors were encountered: