You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Though it occurs to me perhaps we could generate documentation "side-wide" for all installed crates as an independent function, the risk of doing that is its prone to failure, the same failures one can expect if you don't gate the rustdoc behind use doc .... because it has to compile.
And "compiling" currently means "all optional and target-specific dependencies need to be installed", so unless you carefully patched that out, you'll have failures.
The text was updated successfully, but these errors were encountered:
kentfredric
added
the
discussion
ideas, thoughts and meta issues that may or may not eventually lead to some concrete change
label
Feb 10, 2020
kentfredric
changed the title
[discussion] Work out how we're going to rustdoc
Work out how we're going to rustdoc
Feb 10, 2020
My initial thoughts were that we do:
But it needs some thinking about, partly because that approach will create a lot of waste in the form of per-ebuild copies of various things ...
Though it occurs to me perhaps we could generate documentation "side-wide" for all installed crates as an independent function, the risk of doing that is its prone to failure, the same failures one can expect if you don't gate the
rustdoc
behinduse doc
.... because it has to compile.And "compiling" currently means "all optional and target-specific dependencies need to be installed", so unless you carefully patched that out, you'll have failures.
The text was updated successfully, but these errors were encountered: