Specializations, typedef Aliases, and the Per-Specialization Static Gotcha: Pitfalls

Pitfalls and red flags

• Assuming typedef of two different parameter sets points to one shared static.

• Reading only one specialization's static and calling it a global count.

• Refactoring to typedef names and accidentally creating a new parameter set elsewhere.

• Expecting Java generic static behavior when writing SV parameterized code.

Related topics

• Back to Specializations, typedef Aliases, and the Per-Specialization Static Gotcha