Re: Mono-D 1.9 - opIndex/opSlice overload recognition + completion
On Wed, 16 Apr 2014 20:15:21 -0700, Kapps opantm2+s...@gmail.com wrote: On Wednesday, 16 April 2014 at 22:45:45 UTC, Adam Wilson wrote: On Fri, 04 Apr 2014 07:35:18 -0700, Alexander Bothe i...@alexanderbothe.com wrote: On Monday, 31 March 2014 at 21:41:26 UTC, Théo Bueno wrote: Mono-D seems pretty complete to me now, I was wondering if you are thinking about new major features ? http://mono-d.alexanderbothe.com/mono-d-v1-9-opindexopslice-overload-recognition-completion/ :-) I am getting a Completion Timeout and Xamarin Studio is lagging hard when the completion window pops up... I didn't think my files were that big or complex... I had a similar issue until I disabled mixin and template analysis. It seems to have been getting into an infinite loop somewhere in my code (though I'm not sure where). Interesting, I'll have to try that, the project has a LOT of the same mixin template, and it worked for a while, but as the project has gotten bigger it's timed out... -- Adam Wilson IRC: LightBender Project Coordinator The Horizon Project http://www.thehorizonproject.org/
Re: Mono-D 1.9 - opIndex/opSlice overload recognition + completion
On Thu, 17 Apr 2014 09:56:32 -0700, Adam Wilson flybo...@gmail.com wrote: On Wed, 16 Apr 2014 20:15:21 -0700, Kapps opantm2+s...@gmail.com wrote: On Wednesday, 16 April 2014 at 22:45:45 UTC, Adam Wilson wrote: On Fri, 04 Apr 2014 07:35:18 -0700, Alexander Bothe i...@alexanderbothe.com wrote: On Monday, 31 March 2014 at 21:41:26 UTC, Théo Bueno wrote: Mono-D seems pretty complete to me now, I was wondering if you are thinking about new major features ? http://mono-d.alexanderbothe.com/mono-d-v1-9-opindexopslice-overload-recognition-completion/ :-) I am getting a Completion Timeout and Xamarin Studio is lagging hard when the completion window pops up... I didn't think my files were that big or complex... I had a similar issue until I disabled mixin and template analysis. It seems to have been getting into an infinite loop somewhere in my code (though I'm not sure where). Interesting, I'll have to try that, the project has a LOT of the same mixin template, and it worked for a while, but as the project has gotten bigger it's timed out... I just checked my settings and it was already off. -- Adam Wilson GitHub/IRC: LightBender Aurora Project Coordinator
Re: Mono-D 1.9 - opIndex/opSlice overload recognition + completion
On Fri, 04 Apr 2014 07:35:18 -0700, Alexander Bothe i...@alexanderbothe.com wrote: On Monday, 31 March 2014 at 21:41:26 UTC, Théo Bueno wrote: Mono-D seems pretty complete to me now, I was wondering if you are thinking about new major features ? http://mono-d.alexanderbothe.com/mono-d-v1-9-opindexopslice-overload-recognition-completion/ :-) I am getting a Completion Timeout and Xamarin Studio is lagging hard when the completion window pops up... I didn't think my files were that big or complex... -- Adam Wilson GitHub/IRC: LightBender Aurora Project Coordinator
Re: Mono-D 1.9 - opIndex/opSlice overload recognition + completion
On Wednesday, 16 April 2014 at 22:45:45 UTC, Adam Wilson wrote: On Fri, 04 Apr 2014 07:35:18 -0700, Alexander Bothe i...@alexanderbothe.com wrote: On Monday, 31 March 2014 at 21:41:26 UTC, Théo Bueno wrote: Mono-D seems pretty complete to me now, I was wondering if you are thinking about new major features ? http://mono-d.alexanderbothe.com/mono-d-v1-9-opindexopslice-overload-recognition-completion/ :-) I am getting a Completion Timeout and Xamarin Studio is lagging hard when the completion window pops up... I didn't think my files were that big or complex... I had a similar issue until I disabled mixin and template analysis. It seems to have been getting into an infinite loop somewhere in my code (though I'm not sure where).
Re: Mono-D 1.9 - opIndex/opSlice overload recognition + completion
On Friday, 4 April 2014 at 19:20:18 UTC, Adam Wilson wrote: If that's not possible then it's still nice to know that I am working with a type and not an identifier. I furthermore fixed some reference finding + highlighting bugs, some NREs, an SO regression and some further bugs, they're all part of v1.9.2
Mono-D 1.9 - opIndex/opSlice overload recognition + completion
On Monday, 31 March 2014 at 21:41:26 UTC, Théo Bueno wrote: Mono-D seems pretty complete to me now, I was wondering if you are thinking about new major features ? http://mono-d.alexanderbothe.com/mono-d-v1-9-opindexopslice-overload-recognition-completion/ :-)
Re: Mono-D 1.9 - opIndex/opSlice overload recognition + completion
On Fri, 04 Apr 2014 07:35:18 -0700, Alexander Bothe
i...@alexanderbothe.com wrote:
On Monday, 31 March 2014 at 21:41:26 UTC, Théo Bueno wrote:
Mono-D seems pretty complete to me now, I was wondering if you are
thinking about new major features ?
http://mono-d.alexanderbothe.com/mono-d-v1-9-opindexopslice-overload-recognition-completion/
:-)
I updated from 1.7.3 to 1.9 and I get the following:
Could not load project with unknown item type
'{3947E667-4C90-4C3A-BEB9-7148D6FE0D7C}'
I use Xamarin Studio for work, Version 4.2.3
--
Adam Wilson
GitHub/IRC: LightBender
Aurora Project Coordinator
Re: Mono-D 1.9 - opIndex/opSlice overload recognition + completion
On Fri, 04 Apr 2014 10:21:28 -0700, Adam Wilson flybo...@gmail.com wrote:
On Fri, 04 Apr 2014 07:35:18 -0700, Alexander Bothe
i...@alexanderbothe.com wrote:
On Monday, 31 March 2014 at 21:41:26 UTC, Théo Bueno wrote:
Mono-D seems pretty complete to me now, I was wondering if you are
thinking about new major features ?
http://mono-d.alexanderbothe.com/mono-d-v1-9-opindexopslice-overload-recognition-completion/
:-)
I updated from 1.7.3 to 1.9 and I get the following:
Could not load project with unknown item type
'{3947E667-4C90-4C3A-BEB9-7148D6FE0D7C}'
I use Xamarin Studio for work, Version 4.2.3
I fixed it. I had to manually enable to plugin.
--
Adam Wilson
GitHub/IRC: LightBender
Aurora Project Coordinator
Re: Mono-D 1.9 - opIndex/opSlice overload recognition + completion
On Fri, 04 Apr 2014 07:35:18 -0700, Alexander Bothe i...@alexanderbothe.com wrote: On Monday, 31 March 2014 at 21:41:26 UTC, Théo Bueno wrote: Mono-D seems pretty complete to me now, I was wondering if you are thinking about new major features ? http://mono-d.alexanderbothe.com/mono-d-v1-9-opindexopslice-overload-recognition-completion/ :-) I think I have a syntax highlighting regression. The following code from module core.sys.windows.windows used to be highlighted when used in my own modules in 1.7.3 but is now regular black text: alias LONG HRESULT; -- Adam Wilson GitHub/IRC: LightBender Aurora Project Coordinator
Re: Mono-D 1.9 - opIndex/opSlice overload recognition + completion
On Friday, 4 April 2014 at 17:32:52 UTC, Adam Wilson wrote: I think I have a syntax highlighting regression. The following code from module core.sys.windows.windows used to be highlighted when used in my own modules in 1.7.3 but is now regular black text: alias LONG HRESULT; Well, since your previous version was 1.7.3, I think that I've made this change knowingly. Anyway I surely can get aliases highlighted again.
Re: Mono-D 1.9 - opIndex/opSlice overload recognition + completion
On Fri, 04 Apr 2014 11:44:44 -0700, Alexander Bothe i...@alexanderbothe.com wrote: On Friday, 4 April 2014 at 17:32:52 UTC, Adam Wilson wrote: I think I have a syntax highlighting regression. The following code from module core.sys.windows.windows used to be highlighted when used in my own modules in 1.7.3 but is now regular black text: alias LONG HRESULT; Well, since your previous version was 1.7.3, I think that I've made this change knowingly. Anyway I surely can get aliases highlighted again. If possible it would be nice for aliases to be highlighted per their underlying type, so struct aliases highlight differently than primitive aliases? It would be an interesting way to provide semantic information to the user about what the underlying type actually is... If that's not possible then it's still nice to know that I am working with a type and not an identifier. -- Adam Wilson GitHub/IRC: LightBender Aurora Project Coordinator
Re: Mono-D 1.9 - opIndex/opSlice overload recognition + completion
On Friday, 4 April 2014 at 19:20:18 UTC, Adam Wilson wrote: If possible it would be nice for aliases to be highlighted per their underlying type, so struct aliases highlight differently than primitive aliases? It would be an interesting way to provide semantic information to the user about what the underlying type actually is... Probably would take too much time to resolve deduce each alias' base type. If that's not possible then it's still nice to know that I am working with a type and not an identifier. Sure.
