Ben, On Mon, 2018-05-07 at 15:36 +0000, Ben Albrecht wrote: […] > Mason packages are currently limited to projects as libraries only, so this > is true of all current mason packages. There are plans to expand to > application packages in the future, however.
I am assuming that Mason will follow the Cargo model? (With Cargo src/main.rs indicates a package is an executable, src/lib.rs indicates it is a library. Also src/bin/*.rs are executables.) […] > With 'mason test' still under development, this functionality is not yet > available. However, you can work around this by writing your tests in the > main() procedure. With this approach, compiling and running the module as > the entry point with 'mason build && mason run' will run the test suite. Rust and D both use conditional compilation to have the unit tests in the module sources. They also support separate tests for integration tests. This works well so it would be good if Chapel went that route. My problem of the moment for using the above workaround is that I want to separate standard Chapel tests and ones using Charcoal. -- Russel. ========================================== Dr Russel Winder t: +44 20 7585 2200 41 Buckmaster Road m: +44 7770 465 077 London SW11 1EN, UK w: www.russel.org.uk
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Chapel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-users
