Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Intrinsic docs don't render in rustdoc #19649

Closed
Gankra opened this issue Dec 9, 2014 · 5 comments
Closed

Intrinsic docs don't render in rustdoc #19649

Gankra opened this issue Dec 9, 2014 · 5 comments

Comments

@Gankra
Copy link
Contributor

Gankra commented Dec 9, 2014

This may be a duplicate, but can't find the original if it exists.

See http://doc.rust-lang.org/core/intrinsics/index.html for the problem. Most of the intrinsics are doc'd with stability markers, but none of that shows up. Docs also consequently don't show up in re-exports.
@Gankra Gankra added the A-docs label Dec 9, 2014
@lifthrasiir
Copy link
Contributor

Uh, are you sure? The corresponding source code doesn't seem to have stability markers at all. Reexports would be a different story though.

@Gankra
Copy link
Contributor Author

Gankra commented Dec 9, 2014

The copy_memory ones do.

@lifthrasiir
Copy link
Contributor

Ah, you are right. It seems that any extern fns (and not only extern "rust-intrinsics") with stability markers are missing them.

@tomjakubowski
Copy link
Contributor

To clarify: functions declared inside an extern block are missing stability markers. Extern functions have them. That is:

pub extern { #[deprecated] fn foo(); } // missing stability marker
#[deprecated] pub extern fn foo() {} // has stability marker

tomjakubowski added a commit to tomjakubowski/rust that referenced this issue Dec 20, 2014
@tomjakubowski
metadata: Encode attrs for foreign items.
44f6f52 
Related to rust-lang#19649 and rust-lang#16289
@tomjakubowski tomjakubowski mentioned this issue Dec 20, 2014
Merged
@bors bors closed this as completed in fb9b451 Dec 22, 2014
@Eh2406
Copy link
Contributor

Eh2406 commented Sep 6, 2017

There is a FIXME related to this issue,
https://github.com/rust-lang/rust/blob/master/src/libcore/ptr.rs#L30
Now that the issue is closed can the FIXME be fix, or made more specific?

@oli-obk oli-obk mentioned this issue Sep 6, 2017
Open
nivkner added a commit to nivkner/rust that referenced this issue Sep 30, 2017
@nivkner
address some FIXMEs whose associated issues were marked as closed
ff99111 
remove FIXME(rust-lang#13101) since `assert_receiver_is_total_eq` stays.
remove FIXME(rust-lang#19649) now that stability markers render.
remove FIXME(rust-lang#13642) now the benchmarks were moved.
remove FIXME(rust-lang#6220) now that floating points can be formatted.
remove FIXME(rust-lang#18248) and write tests for `Rc<str>` and `Rc<[u8]>`
remove reference to irelevent issues in FIXME(rust-lang#1697, rust-lang#2178...)
update FIXME(rust-lang#5516) to point to getopts issue 7
update FIXME(rust-lang#7771) to point to RFC 628
update FIXME(rust-lang#19839) to point to issue 26925
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@lifthrasiir @tomjakubowski @Gankra @Eh2406