Repository navigation
Exporting a nonexistent item does not cause compilation to fail #2938
Description
Here's the revised test case from #1908. It used to just crash with a poor error message, but now it doesn't fail at all despite the lack of anything named output_styl.
export output_format;
export output_styl;
export config;
#[doc = "The type of document to output"]
enum output_format {
#[doc = "Markdown"]
markdown,
#[doc = "HTML, via markdown and pandoc"]
pandoc_html
}
#[doc = "How to organize the output"]
enum output_style {
#[doc = "All in a single document"]
one_doc,
#[doc = "Each module in its own document"]
doc_per_mod
}
#[doc = "The configuration for this rustdoc session"]
type config = {
output_dir: &str,
output_format: output_format,
output_style: output_style,
pandoc_cmd: option<&str>
};
Compiled with rustc --lib 1908.rs.
Activity
jdm commentedon Jul 17, 2012
Traditionally that has simply triggered a warning message, not a failure as far as I know.
catamorphism commentedon Jul 17, 2012
I'll look at this too. I know it has been just a warning in the past, but IMO it should be a failure.
catamorphism commentedon Jul 18, 2012
Postponed because we're replacing exports with
pubqualifiers on individual items, as per #1893.catamorphism commentedon Oct 6, 2012
Obsolete now that #1893 is implemented. You can't export a non-existent item, since an export is part of an item itself. What joy!
Migrate `rvalue` and `coercion` module to use StableMIR (rust-lang#2938)
Merge pull request rust-lang#2938 from aland-omed/docs/neovim-workspa…
Merge rust-lang#2938