Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Deprecate TF_FOR_ALL #80

Open
superfunc opened this issue Oct 14, 2016 · 2 comments
Open

Deprecate TF_FOR_ALL #80

superfunc opened this issue Oct 14, 2016 · 2 comments

Comments

@superfunc
Copy link
Contributor

The TF_FOR_ALL macro is no longer necessary in most cases, and can be replaced with C++11's range-for.

cc @PeterShinners
@superfunc superfunc changed the title Deprecate TF_FOR_ALL Deprecate TF_FOR_ALL Oct 14, 2016
@superfunc superfunc changed the title Deprecate TF_FOR_ALL Deprecate TF_FOR_ALL Oct 14, 2016
@jtran56
Copy link

jtran56 commented Oct 17, 2016

Filed as internal issue #138793.

@alexwheezy alexwheezy mentioned this issue Jun 19, 2017
Closed
This was referenced Jan 28, 2018
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
@Felix-Kit Felix-Kit mentioned this issue Feb 9, 2022
Closed
@nvmkuruc nvmkuruc mentioned this issue Mar 5, 2024
Open
2 tasks
AdamFelt pushed a commit to autodesk-forks/USD that referenced this issue Apr 16, 2024
@PierreWang
Fix shader load problem (PixarAnimationStudios#80)
6f1ea70 
(cherry picked from commit fb1e43fa2a0c466b199f30a70761276d9f284c09)
@Cewein
Copy link

Cewein commented Dec 27, 2024 •
edited
Loading

I guess this is still relevant, with a quick search I see there is a lot of file still using TF_FOR_ALL. I will jump on the bandwagon and help you @superfunc

there is also the case of the TF_REVERSE_FOR_ALL that can be discused I guess.

@Cewein Cewein mentioned this issue Dec 27, 2024
Open
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@superfunc @jtran56 @Cewein