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.

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

Actually use JSON storage for JSON data #1237

Merged
merged 3 commits into from
Jul 2, 2018

Conversation

sgrif
Copy link
Contributor

@sgrif sgrif commented Jan 18, 2018

We also never use features as a HashMap<String, Vec<String>>, so we
can just pass it through from the database in a lower level
representation.

We also never use `features` as a `HashMap<String, Vec<String>>`, so we
can just pass it through from the database in a lower level
representation.
@carols10cents
Copy link
Member

carols10cents commented Jan 25, 2018

Seems fine. The only thing I can think of this affecting is this as-yet-unimplemented feature request to display a crate's features on its page, and that would be from JSON anyway.

Clarifying for anyone looking at this that this only affects getting a crate's features (per-version) into and out of the crates.io database, and does not touch the serialization to the crates.io index (which happens in git.rs.

bors: r+

bors-voyager bot added a commit that referenced this pull request Jan 25, 2018
1237: Actually use JSON storage for JSON data r=carols10cents

We also never use `features` as a `HashMap<String, Vec<String>>`, so we
can just pass it through from the database in a lower level
representation.
@bors-voyager
Copy link
Contributor

bors-voyager bot commented Jan 25, 2018

Build failed

@sgrif
Copy link
Contributor Author

sgrif commented Jan 25, 2018 via email

@carols10cents
Copy link
Member

bors: r+

bors-voyager bot added a commit that referenced this pull request Jul 2, 2018
1237: Actually use JSON storage for JSON data r=carols10cents

We also never use `features` as a `HashMap<String, Vec<String>>`, so we
can just pass it through from the database in a lower level
representation.

1439: Bump `env_logger` r=carols10cents



1441: `dyn` all the things r=carols10cents

`#![deny(bare_trait_objects)]` is added and all existing trait objects
are documented with the `dyn` keyword.
@bors-voyager
Copy link
Contributor

bors-voyager bot commented Jul 2, 2018

Build succeeded

@bors-voyager bors-voyager bot merged commit 28c25ac into rust-lang:master Jul 2, 2018
@sgrif sgrif deleted the sg-json-for-json branch July 18, 2018 20:04
@Turbo87 Turbo87 added C-internal 🔧 Category: Nonessential work that would make the codebase more consistent or clear A-backend ⚙️ labels Mar 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-backend ⚙️ C-internal 🔧 Category: Nonessential work that would make the codebase more consistent or clear
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants