Chris Povirk

Results 118 issues of Chris Povirk

The subscripts in https://jspecify.dev/docs/spec/#substitution render fine on my desktop, but they're squares (though I think maybe _subscript_ squares? I'd have to check) on my phone. Maybe we can force another...

specification

@wmdietl [said](https://github.com/jspecify/jspecify/pull/678#pullrequestreview-2355768117): > Using some open mdformat would allow us to check formatting in CI and allow all of us to reformat the document before pushing. @netdpb and I have...

https://github.com/jspecify/jspecify/pull/620/files#r1746129824 We currently discuss only what _other elements_ are enclosed by.

specification

For spec 0.3, we said that annotations anywhere in implementation code were "unrecognized," which at the time was a broader category that contained not only "bad" locations (e.g., `class Foo...

specification

@msridhar dug up https://www.oracle.com/technical-resources/articles/java/ma14-architect-annotations.html, and @netdpb pointed out that we have [a glossary entry](https://docs.google.com/document/d/1nbTnJ0-HubLnQPKSjK5CDZyoe6Al64vdlkoJxaYX9XY/preview?resourcekey=0-ADjPZnp8LN3dRX_ptjlagw#bookmark=id.e1wg9ys7ch8l), which eventually leads to http://github.com/jspecify/jspecify/wiki/type-usages. The niche I'm looking to fill is "Why should I use...

documentation

https://github.com/jspecify/jspecify/pull/650 arguably ruled that it is like `? extends @NonNull Object`, though it's not clear that that applies over the existing rules for `` in https://jspecify.dev/docs/spec/#unbounded-wildcard, since there is no...

specification

Currently, the spec uses `T OPERATOR`. https://github.com/jspecify/jspecify/pull/652#pullrequestreview-2316708277 suggests Toperator \[edit: err, with one or both parts of that in code font\]. Note that I had to type that as "`Toperator`."...

specification

I feel like I wrote notes about this somewhere recently, but if so, I can't immediately find them. - "Nullness subtyping" sounds like it ought to be the entire JSpecify...

specification

(perhaps in general but notably in the spec) I think we discussed this at least one. The reasoning may largely have been that "scope" means a lot of things in...

specification

I've gotten questions about it from both @kevinb9n ("JSpecification - kevinb review copy") and @netdpb ("dpb questions about the JSpecify nullness spec"). (We could _maybe_ avoid this if we change...

specification