Dataization of object without `@` attribute

[Chamber6821]

Description of atom dataized explains how will be dataized that decorates something looks like bytes, for example

[] > five
  5 > @
  [] > ignored-attribute

(dataized five).as-bytes > result

result will be equal 00-00-00-00-00-00-00-05

but the description does not explain how object without @ will be dataized, for example:

[] > obj
  1 > one
  2 > two
  3 > tree

(dataized obj).as-bytes > result

What is result equals to?

[github-actions[bot]]

@Chamber6821 thanks for the report, here is a feedback:

Problems

• The bug report's description lacks necessary detail and context.
• The expected and actual behavior is not specified in the bug report.
• The bug report fails to provide any steps for reproducing the issue.

Suggestions

• Provide Detailed Context: Include more specifics about the bug. Try to explain where and when it occurs and what module, feature, or functionality it affects. Also, clarify what you mean by "Dataization" of an object and the significance of the @ attribute.
• Specify Expected and Actual Results: Clearly define what the expected outcome should be when the object is "dataized." In contrast, describe what is currently happening. This will help others understand what's going wrong.
• Include Steps to Reproduce: To make it easier for the team to replicate the issue, provide a step-by-step guide to reproduce the bug. It might be helpful to include things like the environment in which the bug occurs (e.g., a specific software version or operating system), any preconditions that must be met, and the exact inputs or actions that trigger the bug.
• Use Proper Formatting and Organization: Make sure the report is easy to read and understand. Break down the information into clear, succinct sections. Consider using bullet points, headers, or other formatting tools to organize your points.
• Use Clear and Concise Language: Avoid jargon unless necessary, and make sure to explain any terms that others might not be familiar with. Be as clear and concise as you can be to ensure that anyone reading the report can understand the problem.
• Include Screenshots or Code Snippets if Possible: Visual aids can help others understand the issue more quickly. If the problem involves code, consider including relevant code snippets in your report.

Please fix the bug report in order it to get resolved faster. Analyzed with gpt-4

[maxonfjvipon]

@Chamber6821 it's not really responsibility of object dataized. Dataization is the process of taking Δ attribute from the object. "Taking an attribute" is also called "dynamic dispatch" or "dot notation". Here should be described how it works, and also how decorators work. All possible cases for "taking an attribute from the object" should be there:

1. attribute is present in the object
2. attribute is absent, but @ attribute is present
3. attribute is absent, but object is an atom
4. attribute is absent and object is not an atom and @ attribute is absent

If there are not, let us know, we'll improve this paper

[yegor256]

@maxonfjvipon @Chamber6821 it seems that "dataization" is confused with "serialization" here. Maybe we should explicitly say in the doc block of the dataized object that it doesn't serialize an object?

[maxonfjvipon]

@yegor256 what is serialization in terms of EO?

[yegor256]

@maxonfjvipon there is no such thing in EO, but people get confused since they believe there is.

[Chamber6821]

@yegor256 yes, I do not understand what difference between dataozation and serialisation and the description or tests does not helping me to understand difference. I think difference between dataization and serialisation should be explain via small tests and description should pay attention to tests.

Now tests does not explain next edge cases:

1. What happens with objects without @ attribute?
2. What happens with objects with infinity recursion in definition of @?
3. What happens with object that decorates object without @?

It is also worth paying attention in the description that dataization is not serialisation and why. Explain main difference between them. Now dataized looks like wrapper that "call" and save obj.as- bytes.

[yegor256]

@maxonfjvipon maybe we can write a small blog post about the dataized object, with examples?

[maxonfjvipon]

@yegor256 I think we need a blog post which explains what is dataization at all

[Chamber6821]

When will I be able to read the post?

[maxonfjvipon]

@Chamber6821 soon @yegor256 let's move this ticket to https://github.com/objectionary/news.eolang.org