Andrew Ackerman

Out of curiosity, I looked at the IL generated from compiling the following C# script: ``` try { ... } catch { ... } finally { ... } ``` The...

@munificent If changing the interface breaks the context to the point that name inference breaks, then that is probably a good thing in the same way that making a breaking...

> A possible compromise could be: allow to replace enum class name with the keyword "enum". E.g. instead of writing > `CompassPoint.north` write `enum.north`. > It can be resolved according...

> > I don't know if `#` by itself is used for anything right now. > > It's used by symbol literals. That's another feature that doesn't carry its weight...

That seems even more than less than unhelpful... and incredibly convoluted.

In the more general related ticket, I posted my solution to the gradient problem: https://github.com/imaNNeo/fl_chart/issues/285#issuecomment-1553507717 That solution would probably work well here by using that solution together with a gradient...

I think that, as the game currently stands, this would have to be an extremely late game thing. In my game, I've gotten to the point where I can unlock...

How about rather than trying to detect if the browser is on a mobile device, why not try and detect if the input is touch-based?

As far as I can tell, that's what you would have to do anyway, if you want the same website to be usable on both desktop and mobile.

I like the idea of having an `Array` class to logically separate non-growable "arrays" and growable "lists", since it would also bring Dart inline with many other typed languages that...