Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@enescakir
Copy link
Member

@enescakir enescakir commented Feb 6, 2024

Pass hop exception to the custom rspec matcher

We use a custom rspec matcher to verify hop events. In certain tests,
it's necessary to examine the details of the hop exception. Therefore,
we've made a change to pass the hop exception to the rspec helper,
enabling us to check the exception details within the rspec matcher.

Allow to link back to another label for continuation of push

Pushing is becoming popular these days. If you're budding a single prog
and don't require concurrency, push is a better option than bud.

At present, its usage pattern is complex. You need to check the retval
of push in the same label you pushed, then move to the next label.

However, we can simplify this by allowing a link back to another label
for the continuation of push. This way, the pushed program returns the
next label instead of the previous one.

Fixes #1187

@enescakir enescakir self-assigned this Feb 6, 2024
Copy link
Member

@byucesoy byucesoy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great overall 👍

@byucesoy
Copy link
Member

PostgresServerNexus::update_superuser_password also has retval check (which is added after this PR)

@enescakir enescakir force-pushed the push-return-link branch 2 times, most recently from 97576c6 to 7b51464 Compare February 22, 2024 08:28
@enescakir enescakir marked this pull request as ready for review February 22, 2024 08:28
@enescakir
Copy link
Member Author

@fdr @byucesoy it's ready to review

fdr
fdr approved these changes Feb 23, 2024
Copy link
Collaborator

@fdr fdr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can next_label be required? maybe the old retval form has no virtues and should be eliminated.

@enescakir
Copy link
Member Author

can next_label be required? maybe the old retval form has no virtues and should be eliminated.

If the prog runs and returns some values, it could be helpful. Of course, we might be able to find an alternative solution.

@enescakir enescakir requested a review from fdr February 27, 2024 11:04
@fdr
Copy link
Collaborator

fdr commented Feb 27, 2024

can next_label be required? maybe the old retval form has no virtues and should be eliminated.

If the prog runs and returns some values, it could be helpful. Of course, we might be able to find an alternative solution.

Can't the continuation also look at retval ? (we could rename it or leave it as a slight abuse of notation)

Copy link
Collaborator

@fdr fdr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just my question on retval/continuation/etc, leaving this review so it clears my query

Base automatically changed from push-instead-bud to main May 14, 2024 06:59
enescakir added 2 commits July 2, 2024 19:59
We use a custom rspec matcher to verify hop events. In certain tests,
it's necessary to examine the details of the hop exception. Therefore,
we've made a change to pass the hop exception to the rspec helper,
enabling us to check the exception details within the rspec matcher.
Pushing is becoming popular these days. If you're budding a single prog
and don't require concurrency, push is a better option than bud.

At present, its usage pattern is complex. You need to check the retval
of push in the same label you pushed, then move to the next label.

However, we can simplify this by allowing a link back to another label
for the continuation of push. This way, the pushed program returns the
next label instead of the previous one.
@enescakir enescakir marked this pull request as draft October 16, 2024 11:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add call with continuation option for push

4 participants