Update to Manifest Format section in README.md#175
Open
Aizakkuz wants to merge 3 commits intoUpliftGames:mainfrom
Open
Update to Manifest Format section in README.md#175Aizakkuz wants to merge 3 commits intoUpliftGames:mainfrom
Aizakkuz wants to merge 3 commits intoUpliftGames:mainfrom
Conversation
This additional information felt necessary because not everyone knows what a `manifest` file is, and giving some background information might help solidify that understanding even more. Before understanding this background information, this felt like a completely new concept. When I just recently started reading the Rust Programming Language Book cover to cover, I noticed that quite a bit of what is given here began to click extremely well.
This additional information felt necessary because not everyone might be familiar with the term 'manifest file' in the context of a package manager. Providing some background information could help solidify that understanding even further. Before delving into this background information, the concept felt entirely new to me. It wasn't until I recently began reading The Rust Programming Language Book from cover to cover that many pieces of the puzzle began to fall into place. While there's [this source](https://en.wikipedia.org/wiki/Manifest_file) that provides a general description of a 'manifest file,' it doesn't delve into its connection to Rust, and the Cargo package manager. Linking everything back to Rust and Cargo seems quite fitting.
This felt necessary, as that sentence felt slightly redundant. Package manifest file was effectively defined above, so that sentence wouldn't remove much substance if it were cut out.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This additional information felt necessary because not everyone might be familiar with the term 'manifest file' in the context of a package manager. Providing some background information could help solidify that understanding even further.
Before delving into this background information, the concept felt entirely new to me. It wasn't until I recently began reading The Rust Programming Language Book from cover to cover that many pieces of the puzzle began to fall into place.
While there's this source that provides a general description of a 'manifest file,' it doesn't delve into
wally.toml's connection to Rust, and the Cargo package manager. Linking everything back to Rust and Cargo seems quite fitting.