Quinton Miller

This: ```crystal Foo.new.host=("host") Foo.new.host=("host").set_value("id", 10) ``` is parsed as: ```crystal Foo.new.host = ("host") Foo.new.host = ("host").set_value("id", 10) ``` This is inconsistent with the short block form (`&.host=("host")` works just fine)....

IIRC they rejected it because Ameba is strictly limited to syntactic analysis and this requires type inference.

A method with a `Nil` return value restriction may still explicitly return `nil` itself or any other expression whose type is `Nil` or `NoReturn`. A simple syntax check suggests that...

This issue stemmed from the fact that the use of non-blocking `IO.pipe`s blocks certain standard library specs on Windows (see what I did there?), and those specs obviously do not...

> That is, after `debugger` is reached, the user types "a" on the console, and they expect to get "1" as the output. #12119 does this for LLDB. We could...

I think users should be able to write their own expectation classes for the standard library's `Spec`. (I did this once for the compiler's own specs.) The expectation object's interface...

We should allow multiple annotations on the same line: ```crystal @[Nullable] @[Unique] @[Default(0)] @[Type(smallint)] property my_key ``` There is no need to expand the syntax of a single annotation node...

One thing not mentioned is the ability to ignore the newline between the annotation and the annotated node. This makes some things possible: ```crystal def fact(x) if @[Likely] x >...

Something I wonder is what the signature for a lib struct's constructor should look like: ```crystal lib Foo struct Bar x : Int32 y : Bar* end end # Error:...

In case you are wondering, `$stdin.gets.chomp` _does_ error in Ruby Typeprof: ``` $ cat rbstest.rb $stdin.gets.chomp $ rbs method IO gets ::IO#gets defined_in: ::IO implementation: ::IO accessibility: public types: (?::String...