Harald van Dijk

> I think I see why you're doing this - do you then continue with the parse, after an allocation failure? After an allocation failure I still end the parse...

Oh! This is a bit nasty, but we do actually have a way to run cleanup code without modifying sid: all sid-generated exceptions are guaranteed to be preceded by the...

Here's the `RESTORE_LEXER` hack: https://github.com/katef/libfsm/commit/8dfe6124892aa18b826c9193f8c265f3aa6d26e9 (comment edited to point to an updated version) ! This builds on the refcounted expression trees I had already implemented on another branch. Beware, it's...

Yeah, it is quite nasty. It manages to keep a relatively clean parser.sid though, so it does have that going for it.

> I could imagine adding a `%destructors%` style section to sid, to provide action for freeing each type. But honestly I don't want to put the work into that, when...

I just had a realisation that there is another way to keep track of constructed nodes, without a pool, without sid extensions, and without resorting to hacks: just keep a...

Generally, it's not undefined, but not entirely well-defined either. C90 does not require two's complement; the value of `1

Note that this *is* technically an overflow in Rust, that much is right: `-128_i8` is the negation of the integer literal `128_i8`, and `128_i8` is out of range for type...

The dynamic filtering pane suggested by @anewuser is only available for advanced users, but it's the rest of the users that need protection the most. Would it be possible and...

> Struggled today with this, problem is that the unix "strptime" doesn't support milliseconds. As such, I switched to using a regex replace > > ``` > .last_updated |= sub("(?.*)\\..*Z";...