www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.learn - when should ranges be static

I have template hell code; eventually 5 nested range calls have 
dual context-y issues and maybe compiler bugs; adding static 
makes those errors go away, adding static to everything makes new 
bugs.

Wack-a-mole when the compiler gets confused about context is not 
a long term solution and for all I know, wont even be stable.

---

 foo is a nested function and cannot be accessed by bar
When foo and bar are a top level range functions; this error is nonsense, but im treating it like a dual context error because it seems to act that way. --- https://github.com/crazymonkyyy/ref-algorithms/blob/master/refalgorithm.d
Feb 06