Re: "who wants the compilation to continue after illformed JSon that you try to
eval at compile time?"
What I was trying to do is use staticExec to run some other process, then parse
the output string. The compilation definitely should fail when the parse fails,
but I thought it would be nice t
Which of these alternatives run at compile time? And at comparable compile time
speed?
I know it's unfair but what is linked into the VM as native code runs much
faster.
Why not deprecate/remove marshal for v2? A ton of alternatives exist.
compiler/vmops.nim:
registerCallback c, "stdlib.marshal.toVM", proc(a: VmArgs) =
let typ = a.getNode(0).typ
case typ.kind
of tyInt..tyInt64, tyUInt..tyUInt64:
setResult(a, loadAny(a.getString(1), typ, c.cache, c.config,
c.idgen).intVal)
of ty
Ok, to get started, any pointers to where in the compiler source to look to
figure out why it's doing this?
I came across an unintuitive behavior when writing a macro, where a
JsonParsingError thrown by `marshal.to` was not catchable, even though it was
placed in a try...except block.
Code
import marshal
macro caught() =
try:
raise newException(Exception, "bl
