Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

list.eo:208-211: The object does not work. After moving... #3262

Open
0pdd opened this issue Jul 11, 2024 · 2 comments
Open

list.eo:208-211: The object does not work. After moving... #3262

0pdd opened this issue Jul 11, 2024 · 2 comments

Comments

@0pdd
Copy link

0pdd commented Jul 11, 2024

The puzzle 3251-7a787eb5 from #3251 has to be resolved:

# @todo #3251:30min The object does not work. After moving `list` object
# to eo-runtime this is the only method which does not work because it's quite
# hard to implement properly, especially after big changes in EO semantic.
# We need to get it done and write some tests for it.

The puzzle was created by Yegor Bugayenko on 11-Jul-24.

Estimate: 30 minutes, role: DEV.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

0pdd referenced this issue Jul 11, 2024
…-to-eo-runtime

feat(#3251): added `sprintf` and `list` to `eo-runtime`
Copy link

@0pdd thanks for the report, here is a feedback:

  • The todo message is vague about what exactly "does not work" referring to the object. It should specify what the issue is or how the object is failing to perform as expected.
  • The todo message mentions that it's hard to implement the method properly, especially after big changes in EO semantic. However, it doesn't explain why it is hard to implement. This information could be helpful for the person who will work on this todo.
  • The todo states "We need to get it done and write some tests for it" but it does not specify what "it" refers to. It should explicitly state what needs to be done and what needs to be tested.

Tips to improve:

  • Clarify what is meant by "does not work". Describe the expected behavior and how the actual behavior differs.
  • Provide some details about why it is hard to implement the method properly. This could include specific challenges or obstacles that have been encountered.
  • Specify what tasks need to be done and what needs to be tested. This could be specific code that needs to be written, bugs that need to be fixed, or areas of the code that need to be tested.

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

@0pdd
Copy link
Author

0pdd commented Jul 11, 2024

@0pdd thanks for the report, here is a feedback: * The todo message is vague about what exactly "doe...

I see you're talking to me, but I can't reply since I'm not a chat bot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant