The most hilarious thing is that the Python code it was erroneously nitpicking was slop gen itself!
The most hilarious thing is that the Python code it was erroneously nitpicking was slop gen itself!
It involves some boilerplate code for loading the generated wasm but I find it is more neatly automated than wasm-bingen/wasm-pack and not CJS & node focused like neon.
It involves some boilerplate code for loading the generated wasm but I find it is more neatly automated than wasm-bingen/wasm-pack and not CJS & node focused like neon.
Commiting an unwrap unchecked like that is semantically like deref of a pointer in Go without knowing it’s valid, not like handling an err.
In both cases it’s an easy mistake of bad practice (esp under pressure). Not bad PL design
Commiting an unwrap unchecked like that is semantically like deref of a pointer in Go without knowing it’s valid, not like handling an err.
In both cases it’s an easy mistake of bad practice (esp under pressure). Not bad PL design
- The tendency to get stuck on tangential issues that have no bearing on the original task.
- The inability to escape mistakes around code block insertion.
- The overcomplication of code to pass tests.
- The inability to understand abstraction.
- The tendency to get stuck on tangential issues that have no bearing on the original task.
- The inability to escape mistakes around code block insertion.
- The overcomplication of code to pass tests.
- The inability to understand abstraction.