Cam Swords
Cam Swords
This needs a test for the `allow` as well
Should we preserve / move the `development/enums/matching` tests to `move_2024/` for the compiler suite as well? It is somewhat redundant, but I often rely on the compiler tests during development.
In addition to PowerShell, try enabling long paths via `git config`: `git config --system core.longpaths true`
Can we simplify this implementation quite a bit? ``` pub struct SavedInfo { parser: Option, expansion: Option, naming: Option, typing: Option, typing_info: Option, hlir: Option, cfgir: Option, } #[derive(Ord, PartialOrd)]...
So the clike documentation cannot be read unless I have a windows development environment set up?
PR closed as both parts have now been landed elsewhere.
> Overall LGTM other than a few nits. @todd-mystenlabs should probably take a look, though I think you meant to tag @tnowacki
> Should we remove the `poison` injection as a part of this PR? Or is that a future PR? @tnowacki That is a future PR -- it seemed easiest, since...
I think I got everything. I had initially just done testing through the move CLI, but stopped and wrote a harness for testing in the compiler now, too.
Closed as of #22297