add specs for Data.define

[lxxxvi]

Hello again 👋

Here's an attempt for Data.define that is related to:

• New core class to represent simple immutable value object. The class is similar to Struct and partially shares an implementation, but has more lean and strict API. [Feature #16122]

I got confused by the Documentation (https://docs.ruby-lang.org/en/3.2/Data.html) that says

define(name, *symbols) → class
define(*symbols) → class

Defines a new Data class. If the first argument is a string, the class is stored in Data::<name> constant.

I believe the define(name, *symbols) is either wrongly documented or not implented. If I read the discussion about the Feature correctly (https://bugs.ruby-lang.org/issues/16122 ), it's not supposed to be implemented, do you agree?

I added a failing test for it nonetheless.

As always, thank you very much for your review. Let me know what else I can improve. 🙌

[eregon]

I believe the define(name, *symbols) is either wrongly documented or not implented.

Yeah the docs are wrong, it's on purpose not there and a legacy thing of Struct.

[eregon]

This reminds I should create an issue to track specs for 3.2 😅

[lxxxvi]

@eregon I applied the changes you suggested, let me know if something is missing or can be improved. Thanks a lot.

[lxxxvi]

Yeah the docs are wrong, it's on purpose not there and a legacy thing of Struct.

I just saw that the documentation has already been updated on master

• [DOC] Fix call-seq for Data.define ruby#7038

Will this be updated in the docs when 3.2.1 is released, or earlier?

[eregon]

See ruby/ruby#7038 (comment)

[eregon]

Thanks!

[eregon]

This reminds I should create an issue to track specs for 3.2 😅

Done now: #1016