Check following example: require "socket" struct Test getter host : String? getter port : Int32? def initialize(@host, @port) end end test = Test.new("127.0.0.1", 3005) TCPServer.new(test.host.not_nil!, test.port) # Following code works # TCPServer.new(test.host.not_nil!, test.port.not…

So we have the def types String, Int32 Int32, _ And the argument types are String, Int32?. The options for changing the types to match are: change #1 from String to Int32 change #2 from Int32? to Int32 Both can be valid suggestions and they involve the same amount of changes. I think the s…

I think it’s a compiler issue? any idea?

I would say this is compiler error, and this overloading is causing the confusion. Reduced: record Test, a : String?, b : Int32? class Foo def initialize(a : String, b : Int32) end def initialize(b : Int32, dummy = true) end end test = Test.new("foo", 1234) Foo.new(test.a, test.b) # => E…

Yes, this is a bug introduced since 1.5.1. record Test, a : String?, b : Int32? class Foo def initialize(a : String, b : Int32) end def initialize(b : Int32, dummy = true) end end test = Test.new("foo", 1234) Foo.new(test.a, test.b) Same reduced code get a not so misleaded error message …

@zw963 Please don’t “at” me. Thank you! I’m not working on Crystal anymore. Only when I reaaaly feel like doing it. The project is now in charge of others.

I’m not working on Crystal anymore. Only when I reaaaly feel like doing it. I consider this is a reaaaaly bad news.

Why? It’s not like I’ve been helping a lot lately. And the language keeps moving forward.

Another way to explain myself: don’t “at” me because I’m not the one that will fix these bugs. I might fix some bugs if I have time and if I find something interesting. But by "at"ing me it might look to others that they should do the same, because I’m the one they should ping. But that’s not true.

I think in general you should only mention somebody if you know they’re interested in that message or answer to them directly. Inflationary use is not good. Arbitrarily pinging people can be considered rude, regardless of their commitment to fixing bugs. There is no connection to asterite in this …

I think if someone finds and confirms a bug, just submit issues directly may be sufficient, this might be more appropriate than “at” someone in the forum.

Misleading error message when type is not match

Help & Support

zw963 November 5, 2022, 6:06pm 5

@asterite Misleading error message when type is not match · Issue #12720 · crystal-lang/crystal · GitHub

Topic		Replies	Views
Trying to understand compile-time type mismatch Help & Support	8	276	December 26, 2024
Doubt about overloading Help & Support	5	134	March 11, 2026
Is String? any special? Help & Support	2	465	August 12, 2019
Automatic conversion of literal numbers? Help & Support	6	510	September 6, 2020
Some thoughts for Crystal arguments default value and type inference Help & Support	2	321	October 29, 2022

Misleading error message when type is not match

Related topics