To be able to use absolute paths from import in TypeScript using Visual Studio Code you should be using next version of TypeScript – typescript@next which is TypeScript v2. For that do the following: Install typescript@next via npm. For installing TypeScript v2.x npm i typescript@next -D In Visual Studio Code i) Go to menu File … Read more
This error also appears often on Mac OS X. With Homebrew this module is disabled by default on installation, so brew install ocaml will not install the Graphics module, probably due to the XQuartz dependency. If you run brew info ocaml, it will tell you that there’s a flag, namely –with-x11, that will “Install with … Read more
I can’t really recommend this solution work-around but it does function. Rather than exporting an object, you use named exports each member. In another file, import the first module’s named exports into an object and export that object as default. Also export all the named exports from the first module using export * from ‘./file1’; … Read more
Let’s start from the beginning. Look at the Package Layout chapter in The Cargo Book. As you can see, your package can contain lot of stuff: a binary (something you can run) or multiple binaries, a single library (shared code), example(s), benchmark(s), integration tests. Package layout Not all of the possibilities are listed here, just … Read more
Macros within the same crate New method (since Rust 1.32, 2019-01-17) foo::bar!(); // works mod foo { macro_rules! bar { () => () } pub(crate) use bar; // <– the trick } foo::bar!(); // works With the pub use, the macro can be used and imported like any other item. And unlike the older method, … Read more
In a mainish module (main.rs, lib.rs, or subdir/mod.rs), you need to write mod a; for all other modules that you want to use in your whole project (or in the subdir). In any other module, you need to write use a; or use a::foo; You’re far from the only person to be confused by this, … Read more
You’ll have to include b.rs somewhere, typically with mod b;. If b is a child of a (instead of being a sibling of a), there are two ways to do this: Recommended: rename a.rs into a/mod.rs and b.rs into a/b.rs. Then you can mod b; in a/mod.rs. Instead, you can just #[path = “b.rs”] mod … Read more
Rust’s module system is actually incredibly flexible and will let you expose whatever kind of structure you want while hiding how your code is structured in files. I think the key here is to make use of pub use, which will allow you to re-export identifiers from other modules. There is precedent for this in … Read more