subject:"\[Issue 620\] Can't use property syntax with a template function"

[Issue 620] Can't use property syntax with a template function

2020-08-10 Thread d-bugmail--- via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=620 --- Comment #9 from Dlang Bot --- dlang-community/DCD pull request #622 "Fix #620" was merged into master: - dbc9d82f708f18354d5ba26e5efbcf2997c6ba11 by Hackerpilot: Update several dependencies. libdparse: Get support for 'throw' as a function at

[Issue 620] Can't use property syntax with a template function

2012-11-12 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=620 Don changed: What|Removed |Added Status|ASSIGNED|RESOLVED Version|D1

[Issue 620] Can't use property syntax with a template function

2012-01-26 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=620 Walter Bright changed: What|Removed |Added Version|0.175 |D1 --- Comment #7 from Walter Bright 2

[Issue 620] Can't use property syntax with a template function

2012-01-26 Thread d-bugmail

Merge pull request #280 from 9rnsr/propDispatch Issue 620 - Can't use property syntax with a template function -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---

[Issue 620] Can't use property syntax with a template function

2011-07-29 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=620 Kenji Hara changed: What|Removed |Added Keywords||patch CC|

[Issue 620] Can't use property syntax with a template function

2011-01-01 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=620 Alex Khmara changed: What|Removed |Added CC||alex.khm...@gmail.com --- Comment #4 from

[Issue 620] Can't use property syntax with a template function

2010-11-26 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=620 Andrei Alexandrescu changed: What|Removed |Added Status|NEW |ASSIGNED CC|

[Issue 620] Can't use property syntax with a template function

2010-10-31 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=620 --- Comment #3 from Simen Kjaeraas 2010-10-31 12:29:14 PDT --- Some hacking about showed me that opDispatch has a workaround for this problem, by using a two-layer approach: template opDispatch( string name ) { auto opDispatch( T... )( T a