Robin Sommer

Yeah, that does look like a bug. There's are some tests for making sure things work across imports, but this may not be covered. Thanks for reporting.

hilti-build goes through intermediary *.hlt files on disk. Unfortunately there are still some issues where those files end up using constructs that the subsequent read cannot parse back in. That's...

Nobody looking at that right now. The two main parts involved here are (1) the printer in `hilti/passes/printer.cc` (which renders an in-memory AST into HILT source code), and (2) the...

High level comment: Not sure I'd recommend moving to C++20 right now honestly. I'm actually glad that we finally seem to have all compilers under enough control to not have...

This example should be doable, but one note to double-check: I don't think it'd work with look-ahead but would need to do a direct match on the literal. I.e, it...

Here is a version of what I meant. In addition to your example,I think (hope ...) we could also support the following: ``` module test; public type PDUs = unit...

> I suspect I will be prodding more about supporting the 8/64 issue though, that does seem fairly important as I think about it more. I'm starting to think maybe...

@Ethanholtking Did that help? Are you working on this?

> string-like functions in bytes become muddy by introducing UTF-16 (functions like startsWith/upper/lower) I don't think they'd get muddy. `startsWith()` takes a `bytes` argument, so that's really just a byte-for-byte...

> The intermediary conversion to UTF-8 is since case conversions would still need to be handled with utf8proc which does only supports UTF-8. Ah, ok, so it's "muddy" in the...