An incomplete idea regarding exceptions and @nogc that I have is
to encapsulate the exception within the returned value. And
whenever the original value is attempted to be read, a check for
the exception is done. In other words, the exception is not
thrown from the place where it is constructed
Moved from Fedora 19 64bit to Manjaro Linux 64bit.
Main reason: AUR + pacman.
B? If so is that described anywhere?
yazd has done some work toward this[1], though I don't know how
functional it is.
[1] https://github.com/yazd/DKit
If it doesn't work then I'd love feedback.
I've just integrated some DUB support, in terms that you can
create sublime
hings like building the
project built in unless you go through a bit of effort).
Someone made a ST plugin for DCD? Is it on Github somewhere?
Yeah, here it is https://github.com/yazd/DKit
There is some dub stuff too on a different branch, but I'll need
to merge that into master and test
On Saturday, 21 December 2013 at 10:34:20 UTC, Jakob Ovrum wrote:
On Saturday, 21 December 2013 at 10:20:58 UTC, yazd wrote:
There is something weird.
How does UFCS compile since the earliest versions?
http://www.luismarques.eu/d/archeology/56CDCBDBE4688E996548A3F39E63843ADEFBF570
It has
There is something weird.
How does UFCS compile since the earliest versions?
http://www.luismarques.eu/d/archeology/56CDCBDBE4688E996548A3F39E63843ADEFBF570
using addr2line. It uses dwarf
debug information to resolve the addresses provided by the
backtrace to line numbers.
https://github.com/yazd/backtrace-d
I also have some code that reads elf and dwarf, but it isn't
pretty. It can do the same thing that addr2line does.
