Conversation
There was a problem hiding this comment.
Shouldn't we give a separate version to this crate now? Also let's fill the description, categories, and keywords
There was a problem hiding this comment.
Maybe we should also add a readme, since that is shown on crates.io
There was a problem hiding this comment.
I did not touch that yet, as well as renaming of the crate. Did we decide on a publishing scheme?
There was a problem hiding this comment.
not sure what you mean, don't you want to publish it to crates.io?
|
|
||
| [features] | ||
| serde = ["dep:serde"] | ||
| path_serde = ["dep:path_serde"] |
There was a problem hiding this comment.
Do we publish this optional dependency as well?
Does not doing so break crates.io?
There was a problem hiding this comment.
I'm not sure... If that is the case, the only option (besides publishing path_serde as well) would be to provide the path_serde implementations in the path_serde crate...
There was a problem hiding this comment.
I'd be in favor of not depending on path_serde.
schmidma
force-pushed
the
dont-hesitate-to-maybe-overcompensate
branch
from
8561922 to
1e86b6e
Compare
schmidma
force-pushed
the
dont-hesitate-to-maybe-overcompensate
branch
from
40f11a7 to
0f8e9a7
Compare
schmidma
force-pushed
the
dont-hesitate-to-maybe-overcompensate
branch
from
0f8e9a7 to
b60caf9
Compare
4 participants
Why? What?
This PR prepares
linear_algebrato be published, cleaning up structure and some naming, as well as providing feature flags and documentation.fixes #1893