Make the API easy to use without macros. #49
Comments
nical
added a commit
to nical/godot-rust
that referenced
this issue
Feb 24, 2018
…n the example that seem to be causing issue godot-rust#49.
nical
added a commit
to nical/godot-rust
that referenced
this issue
Feb 24, 2018
…erties in the example that seem to be causing issue godot-rust#49." This reverts commit 0cc4faf.
nical
added a commit
to nical/godot-rust
that referenced
this issue
Feb 24, 2018
…n the example that seem to be causing issue godot-rust#49.
|
The manual class class registration code is new on par with the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I received the feedback that abusing custom syntax can be intimidating, and make it hard to understand what is happening under the hood. As a general rule of thumb I think that It's best for an API to be easily usable without macros and then on top of that optionally provide some macros to provide extra ergonomics for those who want it.
Let's follow this rule for defining and registering scripts and classes.
The text was updated successfully, but these errors were encountered: