add Protocol::TRY

[ModProg]

• added Protocol::TRY and call it in ?
• add tests
• bikeshed the name

[ModProg]

What would the best place to add a test?

Should we keep TRY as the name?

I just used the hash calling .try() printed, not sure if that is what you
want.

[udoprog]

Naming seems perfect to me.

I just used the hash calling .try() printed, not sure if that is what you
want.

Commented elsewhere that they're randomly generated. I'm not exactly sure how you did the above, but if it's at risk of conflicting with something else in the future it's better to avoid!

cargo run --bin rune -- hash --random

[udoprog]

What would the best place to add a test?

Sorry, missed this. In the rune crate. I moved the tests in here so that they can make use of pub(crate) items and compile faster (linking is exceedingly slow on some platforms).

You can see a bunch of tests in crates/rune/src/tests. Just remember to add the module in tests.rs.

[ModProg]

I'll add a test later, already tested it in my project and it works!

[udoprog]

Cheers!