- Jun 19, 2021
-
-
Dzmitry Malyshau authored
-
- Jun 18, 2021
-
-
João Capucho authored
-
Gordon-F authored
-
Frizi authored
-
Frizi authored
-
Jakob Hellermann authored
-
Jakob Hellermann authored
-
Jakob Hellermann authored
-
Dzmitry Malyshau authored
-
- Jun 17, 2021
-
-
Frizi authored
-
João Capucho authored
-
João Capucho authored
-
João Capucho authored
-
Frizi authored
-
Frizi authored
-
Frizi authored
-
Frizi authored
-
Frizi authored
-
Frizi authored
-
Frizi authored
-
Frizi authored
-
Frizi authored
-
Frizi authored
-
Frizi authored
-
Frizi authored
-
Frizi authored
-
Frizi authored
-
Frizi authored
-
Frizi authored
-
Frizi authored
-
Igor Shaposhnik authored
-
Jim Blandy authored
This comment claims that the following work is being done after global validation, but it actually appears before global validation.
-
- Jun 16, 2021
-
-
Gordon-F authored
-
Gordon-F authored
-
Igor Shaposhnik authored
-
Jim Blandy authored
Naga is now a workspace with `naga` and `cli` as its two members. The default package for cargo commands is `cli`, so that `cargo run` will just run the CLI. However, this has a few unexpected consequences: - Now `cargo test` will just try to run `cli`'s tests, of which there are none. Adding `"."` to the `default-members` list in the workspace's `Cargo.toml` seems to fix this, without breaking `cargo run`. - Even with `"."` added to `default-members`, `cargo test` will build `naga` by default with the features requested for it in `cli/Cargo.toml`: all the front and back ends, but no `serialize` or `deserialize`. This means that our CI job meant to verify no-feature builds isn't doing that job any more. We need to pass `--package naga` to `cargo test` to make it test naga directly.
-
Gordon-F authored
-
Gordon-F authored
-
Gordon-F authored
-
Gordon-F authored
-