Skip to content

Commit 0824bfa

Browse files
Update to say the features are experimental, not undocumented
1 parent 8531cb6 commit 0824bfa

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

posts/no-longer-sorry.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -109,7 +109,7 @@ is clearly about MSVC Windows x86-64. So what about that?
109109
## Tail-calling for Windows
110110

111111
> [!CAUTION]
112-
> The features for MSVC discussed below are to my knowledge, undocumented.
112+
> The features for MSVC discussed below are to my knowledge, experimental.
113113
> They are not guaranteed to always be around unless the MSVC team decide to keep them. Use at your own risk!
114114
115115
These are the preliminary pyperformance results
@@ -151,6 +151,7 @@ on releasing Visual Studio 2026.
151151
This is now listed in the What's New for 3.15 notes:
152152
> Builds using Visual Studio 2026 (MSVC 18) may now use the new tail-calling interpreter. Results on an early experimental MSVC compiler reported roughly 15% speedup on the geometric mean of pyperformance on Windows x86-64 over the switch-case interpreter. We have observed speedups ranging from 15% for large pure-Python libraries to 40% for long-running small pure-Python scripts on Windows. (Contributed by Chris Eibl, Ken Jin, and Brandt Bucher in gh-143068. Special thanks to the MSVC team including Hulon Jenkins.)
153153
154+
This is the [documentation for [[msvc::musttail]]](https://learn.microsoft.com/en-us/cpp/cpp/attributes?view=msvc-170#msvcmusttail).
154155

155156
### Where exactly do the speedups come from?
156157

0 commit comments

Comments
 (0)