Skip to content

rust_task::block_locked and rust_task::must_fail_unlocked naming inconsistency #2864

Closed
@bblum

Description

@bblum

Both of them are "inner" functions that are usually called by wrappers which take a lock around the call, but sometimes can be called directly if the lock is already held.

"block_locked" means "call this when already locked";
"must_fail_unlocked" means "this function doesn't do any locking"

But they mean the same thing. Clean up their names.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-runtimeArea: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflowsC-cleanupCategory: PRs that clean code up or issues documenting cleanup.E-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions