From: "Guido van Rossum" <guido@python.org> > I received this from Glyph. He brings up some interesting use cases > for thunks. I guess it could be used for "on" style event handler > declarations. Hmm, you could even craft your own case statement with > his suggestion: > > switch(expr): > case(val1): > block1 > case(val2): > block2 > default: > block3 > > This actually makes me worry -- I didn't plan thunks to be the answer > to all problems. A new idea that could cause a paradigm landslide is > not necessarily right. I don't exactly get how containment relationships are disambiguated at compilation time? for sure this is bordering macros' expressivity
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4