James Kuszmaul
James Kuszmaul
FWIW, the single-file ts codegen flag I created for #7161 would allow you to work around this, although it does actually generate self-imports (although they are at least correct self-imports),...
@dbaileychess not sure who to ask for review on this, but the code itself is in a state where it can be reviewed. I don't really thing it's current form...
@dbaileychess not sure who to ask for review on this (also the android build is looking flaky?). cc @AustinSchuh as the last known maintainer for flatbuffers bazel rules...
@dbaileychess ping
I'm not sure where the best place for this is, but there also tends to be a bit of statefulness that can be needed to account for some things. E.g.,...
Fully qualified names don't resolve the issue I was noticing--but it could simplify the logic around the already-existing code to handle this with imports. To resolve what I was noticing,...
More explicitly defining lifetimes to have well defined behavior would be nice. Having a well defined behavior for how to implement lazy decoders sounds good. E.g. for flatbuffers I'd like...
Credit goes to @AustinSchuh for this change, I'm just upstreaming it from https://github.com/frc971/971-Robot-Code
> please use left-binding const (i.e. place it on the right) to avoid confusion on what the const refers to. done
And my expectation would be that this would fail to build if the const were overly aggressive (unless there're casts hidden somewhere that are forcing const char's to char's). The...