On Friday, 20 March 2015 at 18:37:57 UTC, Vladimir Panteleev
wrote:
On Friday, 20 March 2015 at 18:36:19 UTC, Vladimir Panteleev
wrote:
On Friday, 20 March 2015 at 18:05:07 UTC, Ivan Kazmenko wrote:
Thanks. I was able to reproduce the workflow you showed in
the gif to the part where an error
On Friday, 20 March 2015 at 18:05:07 UTC, Ivan Kazmenko wrote:
Thanks. I was able to reproduce the workflow you showed in the
gif to the part where an error pop-up (e.g. no property iota
for type int) is followed by suggesting the appropriate fix.
Do I need another tool for that? Colorout
On Friday, 20 March 2015 at 18:36:19 UTC, Vladimir Panteleev
wrote:
On Friday, 20 March 2015 at 18:05:07 UTC, Ivan Kazmenko wrote:
Thanks. I was able to reproduce the workflow you showed in
the gif to the part where an error pop-up (e.g. no property
iota for type int) is followed by
On Thursday, 19 March 2015 at 16:06:31 UTC, Vladimir Panteleev
wrote:
On Thursday, 19 March 2015 at 14:32:53 UTC, Ivan Kazmenko wrote:
Hey, I also happen to use Far Manager and its internal editor,
at least for simple projects. Is that dcheck triggering a Far
plugin? I have a bit of
On Tuesday, 17 March 2015 at 15:11:02 UTC, Ivan Kazmenko wrote:
For the former problem, is there a tool which jumps out and
tells you use Phobos without importing things properly, or
suggests a Phobos import by the name of the stuff.
I did make something simple for myself, but it doesn't work
On Thursday, 19 March 2015 at 10:21:09 UTC, Vladimir Panteleev
wrote:
On Tuesday, 17 March 2015 at 15:11:02 UTC, Ivan Kazmenko wrote:
For the former problem, is there a tool which jumps out and
tells you use Phobos without importing things properly, or
suggests a Phobos import by the name of
On Thursday, 19 March 2015 at 14:32:53 UTC, Ivan Kazmenko wrote:
Hey, I also happen to use Far Manager and its internal editor,
at least for simple projects. Is that dcheck triggering a Far
plugin? I have a bit of experience with Far recording macros,
but didn't try to write a plugin.
It's
Hi,
I was just refactoring a project to compile under 2.067.
The fixes themselves were trivial: just adding import
std.traits; to some files. Apparently its pieces were publicly
imported by another module in 2.066. So, it's the right fix
anyway.
Understanding what happened, however, took
