Omar Kamel
Omar Kamel
Honestly, this and a union-like feature would be great. Macros are cool, but they still suck when it comes to actually emitting code. You can't tell at a glance what's...
> > I keep accidentally passing Future into code blocks. > > Could a lint help? The lint could tell you when you're interpolating a Future in a String. Sure,...
I feel like straight forwarding is best done through the existing forwarding syntax present in factories; Especially since it should be relatively trivial to implement given the existing factory code....
> @TekExplorer wrote, about plain forwarding: > > it should be relatively trivial to implement given the existing factory code. > > I don't think it will be a huge...
I also don't see any reason why argument records would be any more expensive than what we have now, since it's not like we can *do* anything (directly) with records...
I really don't like the idea of a `passed()` function - it implies that parameters hold additional hidden data, when right now they're just variables defined in an unusual place,...
> > it honestly kind of sucks that we couldn't have used that for null from the get go > > Programming without the value `null` would be utterly impossible,...
Hm... Using late to determine if something has been passed in is an interesting possibility. I still don't like that it feels like reflection, but it's better than a `passed()`...
This would certainly be super nice to have. `.await` as a member access is very nice for chaining - though it might look a little odd to do `[].wait.await;` but...
Related to #1231