Alex Light

This is caused by an oversight in the class-redefinition functionality underlying "apply changes" leading j.l.r.Field objects to become invalid. There's not really anything one would be able to do at...

@JakeWharton Only j.l.r.Field objects can end up invalid. Not retaining any will make the problem less likely to occur. There should be no problems with caching Class or Method objects.

Yes. I specifically disabled the MS java extension because it would complain incessantly about not being able to find maven build files and didn't do any completion without them. This...

FYI: This is preventing the use of clang 20 if you want to compile both this and fmtlib with the same cc since fmtlib needs an update to 11.2 to...

Just putting my thoughts from xls-dev in here. Imo this is something we probably want to have a more explicit std magic function for. The rest of dslx is really...

I still kind of prefer the magic-macro version just for pushing the user to think about what they're doing but @proppy's suggestion seems fine to me.

This seems to be an IR that llvm just takes an inordinately long time to process... Setting llvm opt level to 0 results in finishing in

yeah that's basically what I'm thinking of. Issue is that right now we don't really keep track of the old state for anything. Doing any sort of detection when values...

We might want to build off of the work done on https://github.com/google/xls/issues/1239 to support this. We could have an annotation on structs/etc `#[verilog_export("name")]`. We would need to decide how to...

Just for another motivating example an engineer was recently trying to understand how performance of XLS simulator tools compared to verilog. They created a `#[test_proc]` which ran a proc codegen'd...