We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent d0d5c5d commit 45c5c3bCopy full SHA for 45c5c3b
src/content/blog/2025-11-07-new-phone-who-dis.mdoc
@@ -204,6 +204,12 @@ and the tests into one literate-spec and be able to execute the code using
204
whatever tool is called for, but collecting all the results in one place with
205
the source of the literate specs.
206
207
+One other big area that seems like it might be important. Where's the second
208
+best place to put your method types? Well, the first best place is in the Ruby
209
+syntax of course, and you could always just make the typechecker optional. But
210
+the second best place would be in the literate-spec files right next to the
211
+documentation.
212
+
213
### A Virtual Machine by any Other Name
214
215
The saying is, "A rose by any other name would smell as sweet." But there is
0 commit comments