New Issue: Should deprecating a function automatically mark it as "last resort"?

lydia-duncan-github · June 8, 2021, 5:24pm

17881, "lydia-duncan", "Should deprecating a function automatically mark it as "last resort"?", "2021-06-07T22:20:09Z"

Should deprecating a function automatically mark it as "last resort"?

opened 10:20PM - 07 Jun 21 UTC

area: Compiler area: Language type: Design

Engin suggested it, but probably only when we make it a user-facing feature: > …I have needed that in different cases. Where one is deprecating an argument name — you have to make the deprecated function a last-resort. Where the other was I believe where you deprecate a non-generic function in favor of a generic one. And if you pass an argument that’s of the type that’s the argument type of the deprecated version, you want that to be a last-resort.

Engin suggested it, but probably only when we make it a user-facing feature:

Topic		Replies	Views
Bug with explicit query on a generic type in an argument lst Users	2	112	August 25, 2023
Chapel Debugger (Student Project) Developers	3	270	November 5, 2021
Announcing Chapel 1.24.0! Announcements	0	605	March 18, 2021

New Issue: Should deprecating a function automatically mark it as "last resort"?

Related Topics