Nathan West

Results 57 issues of Nathan West

As the author of autocommand, I didn't feel comfortable writing a comparison blurb against argh, but I still wanted to have it listed in the "similar projects" list.

Suppose I'm creating a new rust struct, with some derive attributes at the top. I type: ``` # ``` And TabNine suggests `[derive(Clone, `. This is a good suggestion, but...

Node names and Property keys are described as: > ...a legal [Identifier](https://github.com/kdl-org/kdl/blob/main/SPEC.md#identifier), or a quoted [String](https://github.com/kdl-org/kdl/blob/main/SPEC.md#string). Whereas annotations are described as: > with a single [Identifier](https://github.com/kdl-org/kdl/blob/main/SPEC.md#identifier) in it. Generally throughout...

documentation
enhancement

For the assistance of implementers, I'd like to propose we add a set of terminology to help group related concepts in KDL. Specifically, I'm interested in a unifying term for:...

Currently, in the KDL spec, it doesn't appear to be possible to use properties as a key-value store (ie, comparable to a `HashMap`, because min and max aren't available properties...

question

#### Current Behavior Currently, starship always places its configuration in `$HOME/.config/starship.toml` #### Expected Behavior I'd expect starship to follow the platform conventions for where to store application specific configuration. These...

💬 discussion
🛠️ configuration

I was surprised to discover recently the existence of a hidden `Deserialize::deserialize_in_place` while reading the serde source code. In the docs it's explained: > This method is stable and an...

Currently, `StrDeserializer` doesn't forward `deserialize_newtype_struct` to `visit_newtype_struct`, which means that trivial newtype structs fail to deserialize from it: [playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=398ab1506f13f3a4677678f3209a2bc7). This seems like an obvious case to support, especially since `StrDeserializer`...

The `unsafe` behavior of `Raw` is trivially shown to be unsound. `str` is *required* to be valid UTF-8, and its methods assume that it contains valid UTF-8 for the purpose...

The following is unexpected behavior: ``` url1 = URL("http://www.example.com/foo?bar=10") url2 = url1.with_path("/bar") assert url1.query = url2.query # Assertion fails ``` While I understand the design decision to treat the query...