`YAML::Any#dig` does not accept a string key about crystal HOT 6 CLOSED

@Blacksmoke16 Regarding the type restriction, there are some general inconsistencies. Hash(K, V)#[](key) has no type restriction either, for example (ref #8893).

from crystal.

I think your problem is the .to_h call after YAML.parse, if you remove that it works as expected, otherwise you're using the Hash#dig version.

EDIT: Looks like that works because the YAML::Any version is less restrictive in regards to what you can pass it? 🤷

from crystal.

Yeah, not a bug. You're calling to_h so you get a raw Hash instead of a YAML::Any wrapper around it. That hash expects YAML::Any keys for its #dig method. You probably want to skip to_h and use YAML::Any#dig instead.

from crystal.

Is there anything left to do here?

@Blacksmoke16 could you clarify this comment:

Looks like that works because the YAML::Any version is less restrictive in regards to what you can pass it? 🤷

from crystal.

I think I meant I was thinking that Hash#dig is defined as def dig(key : K, *subkeys), notice the K type restriction. Whereas YAML::Any#dig is implemented as def dig(index_or_key, *subkeys) : YAML::Any without any type restrictions. But I know the latter will end up using the definition of the former internally so not sure sure how it avoids the compiler error when the type of the hash should be essentially the same?

from crystal.

So not a bug?

from crystal.