I for one really like RBS being external files, it keeps the Ruby side of things uncluttered. When I do need types inline I believe it is the editor's job to s

I for one really like RBS being external files, it keeps the Ruby side of things uncluttered. When I do need types inline I believe it is the editor's job to show them dynamically, e.g via facilities like tooltips, autocompletion, or vim inlay hints and virtual text, which can apply to much more than just signatures near method definitions. Types are much more useful where the code is used than where it is defined. I follow a 1:1 lib/.rb - sig/.rbs convention and have projection+ files to jump from one to the other instantly. And since the syntax of RBS is so close to Ruby I found myself accidentally writing things type-first then using that as a template to write the actual code. Of note, if you crawl soutaro's repo (author of steep) you'll find a prototype of inline RBS. + used by vim projectionist and vscode projection extension