Takeshi KOMIYA
Takeshi KOMIYA
### Feature or Bugfix - Refactoring ### Purpose - Fix typo Hello. I'm back from a long break.
Originally, this note was posted to #types channel in the ruby-jp slack from @soutaro.
In Ruby language, developers need to use both "include" and "extend" to implement mix-in having instance methods and class methods. The auto extending module is a well-known technique to realize...
In Ruby language, developers need to use both "include" and "extend" to implement mix-in having instance methods and class methods. The auto extending module is a well-known technique to realize...
refs: https://github.com/ruby/rbs/pull/1226 I also find `annotate:rdoc:*' and `steep:deprecated` and `pure' annotations. I think the former two are not needed to be documented. But it might be better to document the...
To represent methods like `Object#blank?` and `Object#present?` in ActiveSupport, this adds method annotations `primitive:nil?` and `primitive:not_nil?`. They will be considered as same as `nil?` and not `nil?` internally. refs: #472...
How about adding a declaration of method annotations? I'm not sure "method annotations" is the correct word. Please let me know your thoughts.
Add `--with-expectations=PATH` option to the langserver subcommand. It suppresses warnings and info messages using expectations file like check command does. And it helps to users to develop RBS files gradually.
I noticed Steep emit a warning for the code inverting a boolish value. This is bad result. ``` # app.rbs module Kernel def hello?: () -> boolish end ``` ```...