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

[Improvement]: Improve errors for worker sync send and worker receive actions within lock statements #42585

Open
MaryamZi opened this issue Apr 18, 2024 · 0 comments
Labels
Area/Diagnostics Issues related Diagnostics reported by the Compiler. #Compiler Team/CompilerFE All issues related to Language implementation and Compiler, this exclude run times. Type/Improvement

Comments

@MaryamZi
Copy link
Member

Description

$title.

Describe your problem(s)

The errors are currently

using send action within the lock statement is not allowed to prevent possible deadlocks
using receive action within the lock statement is not allowed to prevent possible deadlocks

Describe your solution(s)

Let's change them to something like

using a send action within a lock statement is not allowed to prevent potential deadlock
using a receive action within a lock statement is not allowed to prevent potential deadlock

Related area

-> Compilation

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

@MaryamZi MaryamZi added Type/Improvement Team/CompilerFE All issues related to Language implementation and Compiler, this exclude run times. labels Apr 18, 2024
@lochana-chathura lochana-chathura added the Area/Diagnostics Issues related Diagnostics reported by the Compiler. #Compiler label Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area/Diagnostics Issues related Diagnostics reported by the Compiler. #Compiler Team/CompilerFE All issues related to Language implementation and Compiler, this exclude run times. Type/Improvement
Projects
None yet
Development

No branches or pull requests

2 participants