Just ran into this, which I wasn't expecting:
> DB[:table].freeze == DB[:table]
=> false
This is because the frozen state is stored in the opts hash, and Dataset#==
compares the opts hashes. This might seem reasonable, but it clashes with
Ruby's behavior more generally:
> "string".freeze == "string"
=> true
> [].freeze == []
=> true
> {}.freeze == {}
=> true
Not sure if this should be changed or not, and even if everyone agrees it
should, some people might rely on the old behavior. Maybe something to
revisit in the next major version?
--
You received this message because you are subscribed to the Google Groups
"sequel-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sequel-talk.
For more options, visit https://groups.google.com/d/optout.