-
Notifications
You must be signed in to change notification settings - Fork 33
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
Should Promise.noise()
just return the promise itself?
#130
Comments
Also I need some clarification about the deprecation of var f:Future<String> = if (...) getActualFuture() else Future.NOISE;
f.handle(value -> /* should I check for `null` here? */); To be honest I'd prefer something that is explicitly specified to resolve to a |
The code should not compile with null safety, because And yeah, the |
So does that mean that |
Indeed. The whole point was to have only one value. I think :D |
Hm, I wonder if it makes sense to have a cached instance of |
Why not ;) |
Need this HaxeFoundation/haxe-evolution#10 (comment) ? |
Not necessarily, but it'd be a nice solution :) |
Given that
Noise
hasfrom Dynamic
so this is possible:(and thus there's no guarantee that two
Noise
-typed values are equal)Shouldn't
Promise.noise
justreturn this
to save some allocations?The text was updated successfully, but these errors were encountered: