-
Notifications
You must be signed in to change notification settings - Fork 29
Issues: ferrocene/specification
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.
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
6.4.3: Revisit core::ops::Try
category:content
Issue related to the content of the specification
kind:enhancement
#101
opened Jul 25, 2022 by
pietroalbini
4: Determine which types need to implement which traits
category:content
Issue related to the content of the specification
kind:enhancement
#61
opened Jul 25, 2022 by
pietroalbini
4.11.2: Explain lifetime conformance
category:content
Issue related to the content of the specification
kind:enhancement
#65
opened Jul 25, 2022 by
pietroalbini
4.11.4: Explain pattern inference
category:content
Issue related to the content of the specification
kind:enhancement
#68
opened Jul 25, 2022 by
pietroalbini
4.11.4: Incorporate type coercion into type resolving rules
category:content
Issue related to the content of the specification
kind:enhancement
#73
opened Jul 25, 2022 by
pietroalbini
5: Incorporate mutable place expressions and temporaries
category:content
Issue related to the content of the specification
kind:enhancement
#85
opened Jul 25, 2022 by
pietroalbini
5.1.1: Incorporate borrowing rules
category:content
Issue related to the content of the specification
kind:enhancement
#86
opened Jul 25, 2022 by
pietroalbini
5.1.1: Revisit type inference-related rules
category:content
Issue related to the content of the specification
kind:enhancement
#87
opened Jul 25, 2022 by
pietroalbini
5.1.5: Revisit the support for floating point literals
category:content
Issue related to the content of the specification
kind:enhancement
topic: future compat lint
Issue tracking future compatability lints
#88
opened Jul 25, 2022 by
pietroalbini
6: Indicate required expression context
category:content
Issue related to the content of the specification
kind:enhancement
#93
opened Jul 25, 2022 by
pietroalbini
6: Incorporate borrowing rules
category:content
Issue related to the content of the specification
kind:enhancement
#95
opened Jul 25, 2022 by
pietroalbini
6: Indicate user facing type adjustments
category:content
Issue related to the content of the specification
kind:enhancement
#97
opened Jul 25, 2022 by
pietroalbini
Make paragraph numbers clickable
category:rendering
Issue related to the rendering of the specification (like our theme, the extension, or Sphinx)
kind:enhancement
#50
opened Jul 15, 2022 by
pietroalbini
6.4.1: Determine the proper place for borrowing-related rules
category:content
Issue related to the content of the specification
kind:enhancement
#100
opened Jul 25, 2022 by
pietroalbini
11: Revisit the use of the term "scope"
category:content
Issue related to the content of the specification
kind:enhancement
#108
opened Jul 25, 2022 by
pietroalbini
20.5: Rewrite subchapter
category:content
Issue related to the content of the specification
kind:enhancement
#127
opened Jul 25, 2022 by
pietroalbini
Vague character definition
category:content
Issue related to the content of the specification
kind:enhancement
#135
opened Jul 26, 2022 by
est31
Vague Union Legality Rules (4.4.3)
category:content
Issue related to the content of the specification
kind:enhancement
#141
opened Jul 26, 2022 by
HeroicKatora
How to handle future compatibility lints
topic: future compat lint
Issue tracking future compatability lints
#145
opened Jul 26, 2022 by
bjorn3
Glossary: Unicode definition is either informal or (possibly) incorrect
#156
opened Jul 26, 2022 by
ojeda
#![crate_type] and #![crate_name] aren't allowed inside cfg_attr
topic: future compat lint
Issue tracking future compatability lints
#164
opened Jul 26, 2022 by
bjorn3
Previous Next
ProTip!
Exclude everything labeled
bug
with -label:bug.