Skip to content

[intro.execution] It doesn't seem correct to say "sequenced after the invocation" #8145

@frederick-vs-ja

Description

@frederick-vs-ja

[intro.execution]/15 current reads:

If a signal handler is executed as a result of a call to the std​::​raise function, then the execution of the handler is sequenced after the invocation of the std​::​raise function and before its return.

(The specification was introduced by N3910 which resolved CWG1441.)

It seems that we shouldn't say "sequenced after the invocation", since this usually means "sequenced after exiting the function", and when std::raise normally returns, "sequenced after the invocation" will mean "sequenced after its return".

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions