Yakov K.

As someone who took part in the original "core interfaces" discussion – yes, please!

@felangel thanks for the response! > When using bloc you can make use of emit.forEach and emit.onEach to handle reacting to an incoming stream. This is certainly very true, but...

Hi @Gene-Dana! > Hi there ! This is really something that is highly discouraged due to the declarative nature of the API Sorry, but I think we are talking about...

> I’m aware of this but didn’t think it’s worth bumping the sdk constraint to 2.14 just for this change since this implementation has been untouched for a while now....

Hi @simolus3. Has something changed? The IDE suddenly started working for me perfectly.

Yep, even syntax highlighting :)

Does this feature replace the previous proposal of views?

@timsneath Both type aliases and inline classes can be directly mapped to Haskell's Type synonyms and Newtypes, I think I even saw direct references in the feature specifications. I think...

Having the same issue! Edit: downgrading back to Flutter 2.2.3 seemed to solve it for me. Considering that this bug was discovered at roughly the same time, I suspect it...

Hi @natebosch! Thanks for considering my issue. Sure! Yes, semantically `asyncExpand` and `exhaustMap` both represent higher-order stream mappers, but they have a key difference – while `asyncExpand` would sequentially flatten...