Neil> A motivation for this was that one of the examples Neil> @accepts(int,int) Neil> @returns(float) Neil> def bar(low,high): Neil> which separates related information too much for me. Yes, but when I wrote that example, the list-after-def form was the current king-of-the-hill: def bar(low,high) [accepts(int,int), returns(float)]: ... Looks fine to me. ;-) Skip
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