Explore >> Select a destination
|
You are here 
|
jakevdp.github.io | ||
| | | | |
madebyme.today
|
|
| | | | | Some time ago, during a code review, I had a discussion with a colleague of mine about preferring dict() over {} in new Python code. They argued that dict() is more readable - and expresses intent more clearly - therefore should be preferred. I wasn't convinced by that, but at that time I didn't have any counterarguments, so I passed. Yet that made me wonder: what's the difference between the dict type and {} literal expression? | |
| | | | |
eli.thegreenplace.net
|
|
| | | | | [AI summary] This article explains how to add a new 'until' statement to Python's compiler by modifying its grammar, AST generation, and bytecode compilation processes. | |
| | | | |
akaptur.github.com
|
|
| | | | | Nick Coghlan added another interesting note in response to my last post about creating side-effecting assignments in python. Here's Nick: @ ... | |
| | | | |
cfallin.org
|
|
| | | [AI summary] The article discusses the development of an Ahead-of-Time (AOT) compiler for JavaScript, leveraging precompiled inline-cache (IC) stubs. By moving runtime type binding to indirect calls, the compiler can generate static code, enabling full AOT compilation. This approach achieves significant performance improvements, with a 2.77x geometric mean speedup on various benchmarks. The article also explores further optimizations through profile-guided inlining, and compares this method with other AOT approaches like Hopc's type inference. The potential for future enhancements and the use of compiler backends derived from interpreters are also highlighted. | ||
