_carljm

6 ms·

1.
by _carljm 6mo ago
We provide this diagnostic in ty ( https://docs.astral.sh/ty/reference/rules/#possibly-unresolv... ), but it's disabled by default because it can have false positives in many scenarios where the code works
2.
by _carljm 9mo ago
https://forum.cursor.com/t/newly-published-extensions-appear... suggests that there's some kind of delayed daily update for new VSCode extension versions to become available to Cursor? It seems likely that's
3.
by _carljm 9mo ago
I can reproduce this; we're looking into it.
4.
by _carljm 9mo ago
We'll be adding ourselves to that table soon. We'll have some work to catch up with pyright on conformance, but that's what the time between now and stable release is for.
5.
by _carljm 1y ago
There are ways to type invariant generics more precisely that still meet the gradual guarantee. E.g.: x = [] # list[Unknown] x.append(A()) # list[Unknown | A] takes_list_of_a_or_b(x) # list[A | B] We haven't decided yet i
6.
by _carljm 1y ago
ty also implements gradual set-theoretic types, and can represent "ranged" dynamic types (as intersections or unions with Any/Unknown). We don't currently refine dynamic type based on all uses, as suggested here, though
7.
by _carljm 1y ago
This information is already maintained via `if sys.version_info >= (...):` conditionals in typeshed stubs. I don't think this is important enough to justify maintaining the same information in a duplicate way.
8.
by _carljm 1y ago
I agree that would be nice; probably not near the top of our list right now (and not trivial to implement), but it makes sense. Thanks for the suggestion.
9.
by _carljm 1y ago
Yes, thank you for your graciousness and generosity, very much appreciated.
10.
by _carljm 1y ago
I knew we left something important out of that onboarding document
11.
by _carljm 1y ago
Not the same headline functionality yet, no. At the moment all we support is diagnostics (some of which may be wrong) and go-to-type-definition. More will come.
12.
by _carljm 1y ago
Yes, we've talked; I know a number of the pyrefly devs well. Ty had already been months in development when pyrefly development started. We discussed collaboration, but they decided they needed to do their own thing in order to move qu
13.
by _carljm 1y ago
There's a good chance many of the errors we emit are incorrect, at this stage. Lots to do still!
14.
by _carljm 1y ago
The current version can handle importing pydantic without error just fine, but it probably can't find your virtualenv, so it doesn't know what third-party dependencies you have installed. Ty will discover your venv if it is in `.v
15.
by _carljm 1y ago
Yes, red knot was the internal development code name; ty is the actual name.
16.
by _carljm 1y ago
We're looking forward to hearing what your experience is! There's a certain amount of roughly-constant overhead (e.g. reading all the files), so generally ty will look relatively faster the larger the project is. For very large pr
17.
by _carljm 1y ago
(ty developer here) Currently we default to our oldest supported Python version, in which `datetime.UTC` really doesn't exist! Use `--python-version 3.12` on the CLI, or add a `ty.toml` with e.g. ``` [environment] python-version = &quo
18.
by _carljm 1y ago
(ty developer here) This is an early preview of a pre-alpha tool, so I would expect a good chunk of those 3500 errors to be wrong at at this point :) Bug reports welcome!
19.
by _carljm 5y ago
"Open it and see if there is interest" is the first step in "offer to work to upstream it." Not sure where you got the idea that it's only the former and not the latter.
20.
by _carljm 5y ago
We've been calling it Cinder internally for years, long before we thought about opening it up. If we wanted to make it a big branded thing, we'd work on finding a unique name for that, but we aren't trying to do that, we&#x27
21.
by _carljm 5y ago
We have contributed quite a few parts of cinder upstream already and will continue to do so. I’m not sure where you got the idea that this is just a dump and we expect core devs to do all the work of upstreaming.
22.
by _carljm 5y ago
It’s definitely true that there’s stuff a JIT would love to know that the type system can’t tell you. But that doesn’t mean there isn’t useful information available in type annotations. In particular it is possible to speed up attribute acc
23.
by _carljm 5y ago
Our JIT can use type information when available to improve speed. This is what the Static Python project described in the README is all about.
24.
by _carljm 5y ago
With Static Python we use type annotations in compilation, and we require them to be correct (they are runtime checked at boundaries with non-Static code and throw TypeError if wrong types are passed in.) We haven’t gone the hidden classes
25.
by _carljm 5y ago
It was a few years ago and I didn’t work on it directly, so my knowledge is a bit fuzzy, and I think the person who did work on it is no longer at the company. As best I recall the slog to get it working was mostly about C extensions, but I
26.
by _carljm 5y ago
Static Python is a bit different in that it’s not a subset language. It makes a few semantic changes, most notably that classes are slotified, so you can’t tack random extra attributes into instances. If you’re writing typed Python you prob
27.
by _carljm 5y ago
Or there are just different code paths in the called function (eg a “cache hit” code path and a “cache miss” one), and only some of the code paths need to await.
28.
by _carljm 5y ago
It’s also likely that this change, which is a big win for our prefork production environment, drags down our benchmark results. It makes every incref and decref more expensive.
29.
by _carljm 5y ago
It’s worth noting that we’ve never targeted perf on any of these benchmarks, so these are just the results that fell out from optimizing for our production workload, which is a totally different beast. Most of the hits are due to the defaul
30.
by _carljm 5y ago
Benchmarks are now in a PERF file in the repo.

More ›