Search results

<code>#[track_caller]</code> does not work on <code>fn drop</code>

A-panicArea: Panicking machineryArea: Panicking machinery

C-enhancementCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.

F-track_caller`#![feature(track_caller)]``#![feature(track_caller)]`

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#116942 In rust-lang/rust;

· SludgePhD opened on Oct 19, 2023

Tracking Issue for <code>#[track_caller]</code> on closures

A-closuresArea: Closures (`|…| { … }`)Area: Closures (`|…| { … }`)

C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFC

F-track_caller`#![feature(track_caller)]``#![feature(track_caller)]`

S-tracking-ready-to-stabilizeStatus: This is ready to stabilize; it may need a stabilization report and a PRStatus: This is ready to stabilize; it may need a stabilization report and a PR

T-langRelevant to the language teamRelevant to the language team

Status: Open.

#87417 In rust-lang/rust;

· Aaron1011 opened on Jul 23, 2021

Adding #[track_caller] on #[alloc_error_handler] seems to cause undefined behavior

C-bugCategory: This is a bug.Category: This is a bug.

F-track_caller`#![feature(track_caller)]``#![feature(track_caller)]`

requires-nightlyThis issue requires a nightly compiler in some way.This issue requires a nightly compiler in some way.

Status: Open.

#83430 In rust-lang/rust;

· repnop opened on Mar 24, 2021

Make core::panic::Location available from another module?

C-enhancementCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.

F-track_caller`#![feature(track_caller)]``#![feature(track_caller)]`

T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.

Status: Open.

#72444 In rust-lang/rust;

· anp opened on May 21, 2020

Measure binary size impact of implicit caller location

C-optimizationCategory: An issue highlighting optimization opportunities or PRs implementing suchCategory: An issue highlighting optimization opportunities or PRs implementing such

F-track_caller`#![feature(track_caller)]``#![feature(track_caller)]`

I-heavyIssue: Problems and improvements with respect to binary size of generated code.Issue: Problems and improvements with respect to binary size of generated code.

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#70579 In rust-lang/rust;

· anp opened on Mar 30, 2020

<code>#[track_caller]</code> should inherit through specialization ancestors, too?

A-specializationArea: Trait impl specializationArea: Trait impl specialization

F-specialization`#![feature(specialization)]``#![feature(specialization)]`

F-track_caller`#![feature(track_caller)]``#![feature(track_caller)]`

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

T-langRelevant to the language teamRelevant to the language team

Status: Open.

#70293 In rust-lang/rust;

· anp opened on Mar 23, 2020