-
Notifications
You must be signed in to change notification settings - Fork 11
Array like #154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Array like #154
Conversation
Signed-off-by: Francis Bouvier <francis@lightpanda.io>
Rationale: this feature has nothing to do with the Type init. The idea is to get/set values on the JS object itself after its instantiation. Thoses actions are by definition dynamic and do not affect the underling Type. By consequence the corresponding Zig object will not have those values. Signed-off-by: Francis Bouvier <francis@lightpanda.io>
Signed-off-by: Francis Bouvier <francis@lightpanda.io>
Signed-off-by: Francis Bouvier <francis@lightpanda.io>
|
I'm not happy with the name See my commit msg on f322ae8 |
|
At the end I was able to make this PR without depending on the Zig <> JS object map relation. But of course once we have that we will have to update to call |
What about calling it |
798d128 to
be960ad
Compare
Signed-off-by: Francis Bouvier <francis@lightpanda.io>
Split assertFuncHasParam to assertFuncHasParamT and assertFuncParamIsT Better logic of strict parameter on assertFuncIsMethod Signed-off-by: Francis Bouvier <francis@lightpanda.io>
Closes #126
Relates to #49