i would like to make std testing assert called as std assert as before 🤔
working on it... ♻️

EDIT: locally in my tests

• use std run-tests works as before
• use std assert only imports the assert command
• use std assert equal only imports assert
• use std "assert equal" import assert equal

there is definitely an issue with main commands inside the modules of std 🤔
i could not find a solution so i reverted the changes made to the testting module...
at least all the rest is fixed 😌

Codecov Report

Merging #9193 (a446a38) into main (bf86cd5) will decrease coverage by 0.40%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #9193      +/-   ##
==========================================
- Coverage   68.92%   68.53%   -0.40%     
==========================================
  Files         635      636       +1     
  Lines      102041   102281     +240     
==========================================
- Hits        70332    70097     -235     
- Misses      31709    32184     +475     

I'll merge this because I need to iterate on this in #9245. Seems good to me, it's better not to have the prefixes on the command names.

@amtoine Can you describe the main issue you ran into?

@kubouch

Can you describe the main issue you ran into?

yes i can 💪

Note
the command below are all run from inside cargo run -- -n while being checked out on the revision

✔️ on latest main, i.e. 429c433, if you use std iter, you'll have access to all the iter commands.
you can try hitting tab after iter and see iter find, iter scan, etc, etc, ...

now let's say we want to add a main command to the module to give the help of the module itself

export def main [] { help iter }

at the end of iter.nu
now we get the following behaviours

• ❌ use std iter only import the iter command, which does print some incomplete help
• ❌ use std iter find does not import iter find but only iter, no find to be seen
• ✔️ use std and then std iter works
• ✔️ use std "iter find" does work as expected