Comments (6)
This is one of a number of "improvements" brought by moving the reference into a separate submodule.
Now the nightly reference is updated when someone sends a PR updating that submodule to the main repo, get it merged, and the next nightly happens.
from reference.
That's correct.
In order to not spam the main repo with updates, I plan on doing it once every two or three weeks, along with the book and nomicon repos.
I'm going to keep this ticket open as a "put this into the README", thanks!
from reference.
Can't we release the online, compiled docs separately from the release of nightly rust?
from reference.
Sure, it's possible, but creating yet another duplicate URL for some docs seems like a bad tradeoff to me.
from reference.
It might be best to document this process on the forge since this is cross-cutting and then put a link to that into the readme.
from reference.
https://forge.rust-lang.org/release-process.html is now on the forge, but isn't exactly accessible.
from reference.
Related Issues (20)
- Doucment how raw-dylib finds DLLs at runtime HOT 1
- Possible outdated list of architectures for the support of asm! ? HOT 2
- How to protect meaningful sub type? HOT 2
- should have document on best practice about how to `throw custom error` HOT 3
- [feat] some rust docs example can adopt incorrect-example-vs-correct-example-style
- Default trait object lifetimes section is quite inaccurate HOT 2
- TupleStructPattern misses RestPattern HOT 2
- Guarantee that uninitialized bytes have no bit validity
- types/closure is not accurate. We don't need to use a new variable when capturing a field from a struct HOT 1
- Warn that `repr(packed)` and `repr(align)` do not guarantee field order, and as a result do not guarantee size
- Clarify how types are constructed from function items
- macros-by-example: repetitions, example seems not correct HOT 2
- Document that `Option<char>` has the same size and alignment as `char` on all platforms HOT 1
- UB: Dangling Pointer, ZSTs. HOT 4
- Rust tools HOT 1
- Section on Object Safety does not explicitly mention when Self is a type parameter HOT 1
- Add tests for content-visibility changes and used value of contain. by fred-wang ยท Pull Request #43662 ยท web-platform-tests/wpt ยท GitHub HOT 1
- Should `#[automatically_derived]` docs contain advice for derive macros?
- GitHub - huggingface/transformers: ๐ค Transformers: State-of-the-art Machine Learning for Pytorch, TensorFlow, and JAX.
- `Self` receiver does *not* imply `Self: Sized` HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from reference.