imported modules aren't exported #268
Comments
|
Supported in rustc; buggy in rustboot. Unfortunately I don't think we can easily fix it in rustboot. Need to stick with either redundant declarations or compiler-conditional crate components until after we bootstrap. |
oli-obk
added a commit
to oli-obk/rust
that referenced
this issue
Sep 19, 2017
Split up miri into the librustc_mir and bin parts
keeperofdakeys
pushed a commit
to keeperofdakeys/rust
that referenced
this issue
Dec 12, 2017
linux: Add prlimit(2) and prlimit64(2)
As with `getrlimit` and `setrlimit`, the glibc wrappers have a non-`int`
for the `resource` argument, eg:
extern int prlimit (__pid_t __pid, enum __rlimit_resource __resource,
const struct rlimit *__new_limit,
struct rlimit *__old_limit) __THROW;
dlrobertson
pushed a commit
to dlrobertson/rust
that referenced
this issue
Nov 29, 2018
Match guards are optional
djtech-dev
pushed a commit
to djtech-dev/rust
that referenced
this issue
Dec 9, 2021
Add passthru for 'MergeFunctionsPass'
celinval
pushed a commit
to celinval/rust-dev
that referenced
this issue
Jun 4, 2024
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I have, in
mod1:And then in another mod try to refer to
mod1.foo.[something], I get (with rustboot)"error: the name 'foo' can't be found in the module".Maybe this is by design, but I'd argue that it'd be very good to have this supported (and that it's not hard to support). I ran into this trying to factor out the duplicated native modules in lib/linux_os.rs and lib/macosx_os.rs.
The text was updated successfully, but these errors were encountered: