Meta-issue for discussion of the proposal to add voidness-preservation restrictions

[leafpetersen]

This issue is to provide a forum for community discussion and feedback related to the proposal to add specified static analysis for restricting the ways in which void producing or consuming objects can be used.

This entry will be updated when a proposal is available.

cc @munificent @eernstg @floitschG @lrhn

[brianegan]

Yay, please add this :) It's awkward to create Stream<Null> onButtonPressed and then onButtonPressed.listen((ignoreMe) => doSomething()).

This can be useful for converting argument-less callbacks into Streams, as an example where I've specifically needed it.

[lrhn]

I don't think there is any plan to enable the use of a Function() where a Function(void) is expected.

What you might get is a warning if you use the ignoreMe of voidStream.forEach((ignoreMe) { action(); }); for anything, or if you use do voidStream.forEach(print), which acutally uses the void-typed value.

[natebosch]

@leafpetersen - was this superseded by generalized void work? Are there remaining potential changes to discuss?