Philipp Görz

To add to the response by @Robbepop. There is also the possibility of padding out functions using something like macros as outlined here: https://github.com/phi-go/rfcs/blob/guaranteed-tco/text/0000-guaranteed-tco.md#helpers. Admittedly, this is not as ergonomic...

@doug-moen the feature name is also discussed in this [thread](https://github.com/rust-lang/rfcs/pull/3407#discussion_r1160626278). I'll quote your comment there so that everything is in one place.

@digama0 thank you for clarifying (https://github.com/rust-lang/rfcs/pull/3407#issuecomment-1500620309). I think this would be great to have from a usability aspect. As the implementation does not sound trivial I'll add this suggestion to...

@programmerjake you are right! I was waiting for some feedback on the feature name (https://github.com/rust-lang/rfcs/pull/3407#discussion_r1162478235). Though, I take it your vote is in favor of TCE as the feature name.

> > Though, I take it your vote is in favor of TCE as the feature name. > > tbh I don't particularly care as long as it's not named...

It seems the feature name will come down to popularity, if anyone wants you can vote here: https://github.com/rust-lang/rfcs/pull/3407#discussion_r1166645590.

> @Fishrock123 From what I remember, `become` is reserved specifically _because_ it was always intended to be for _this_ use. Yes, `become` is reserved exactly for this use case, see...

According to my count all raised concerns should be addressed now.