Skip to content

Conversation

epage
Copy link
Contributor

@epage epage commented Jan 26, 2019

This is an experiemnt in a new direction in trying to resolve

The new downsides this introduces

  • No main_binary or cargo_example
  • Can only work within integration tests

We're recommending the use of escargot in these cases which I think
might be reasonable because instead of making policy decisions for the
user, and no one ever being happy, the user can choose which policy they
want. Plus, in more complex cases they should already be using
escargot so they can cache.

Fixes #6
Fixes #57

epage added 2 commits January 26, 2019 16:51
This is an experiemnt in a new direction in trying to resolve
- Cargo overhead (assert-rs#6)
- Compile times from mismatched `--target` (assert-rs#57)
- Suprising behavior if `--target <triplet>` isn't specified (assert-rs#4)

The new downsides this introduces
- No `main_binary` or `cargo_example`
- Can only work within integration tests

We're recommending the use of `escargot` in these cases which I think
might be reasonable because instead of making policy decisions for the
user, and no one ever being happy, the user can choose which policy they
want.  Plus, in more complex cases they should already be using
`escargot` so they can cache.

Fixes assert-rs#6
Fixes assert-rs#57

BREAKING CHANGE: `main_binary` / `cargo_example` no longer exist.  Also,
successfully running `cargo_bin` has been restricted to integration
tests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

main_binary takes minutes on first run main_binary takes ~300ms per invocation
1 participant