Skip to content

Conversation

wilzbach
Copy link
Member

@wilzbach wilzbach commented Feb 3, 2018

For now, run.dlang.io only contains the latest stable release.
This will make sure, that this is selected.
I might build the latest unstable release too over the next days, but not today anymore.

@wilzbach
Copy link
Member Author

wilzbach commented Feb 3, 2018

BTW @9il I saw that many public examples miss the mir.ndslice.slide import.
We could automatically add that one to all example with something like this:

diff --git a/doc/run_examples_custom.js b/doc/run_examples_custom.js index b6ef413..c211279 100644 --- a/doc/run_examples_custom.js +++ b/doc/run_examples_custom.js @@ -21,6 +21,9 @@ function wrapIntoMain(code) { else { codeOut += "void main()\n{\n"; codeOut += " import " + currentPackage + ";\n"; + if (currentPackage !== "mir.ndslice.slice") { + codeOut += " import mir.ndslice.slice;\n" + } // writing to the stdout is probably often used codeOut += " import std.stdio: write, writeln, writef, writefln;\n "; codeOut += code.split("\n").join("\n ");

but I'm thinking that's probably more valuable to potential readers to add the imports in the public unittest directly where needed, s.t. they don't get an error when they copy/paste.
What do you think?

@9il
Copy link
Member

9il commented Feb 4, 2018

Both variants are good for now. The last one is better for general case

@9il 9il merged commit e05a5cf into libmir:master Feb 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants