We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
class Main { static function main() { final test = new Main(); test?.foo(); // ok test?.bool = true; // Invalid operation } public function new() {} public function foo():Void {} public var bool = true; }
I think this can be supported too, like calls? Works in kotlin
The text was updated successfully, but these errors were encountered:
I actually find "assign it if it's not null" a very strange concept, but the += case makes sense to me. So I guess supporting both would be fine.
+=
Sorry, something went wrong.
Oh right it's not about the field being null but the thing we're accessing the field on. So yes both cases make sense.
null
dc453c8
[typer] support safe nav for assign ops
232e3ef
closes HaxeFoundation#11379
Simn
No branches or pull requests
I think this can be supported too, like calls? Works in kotlin
The text was updated successfully, but these errors were encountered: