dawg

4 ms·

1.
by dawg 2y ago
Give git-autofixup a try, never had any incorrect fixup targets with it's hunk-based algorithm.
2.
by dawg 2y ago
Same workflow here, and it's become a breeze with autofix, rebase --update-refs, and a small command to push the whole stack. I'm using magit, so I directly see what could not be matched and remains staged.
3.
by dawg 2y ago
Yes, I empirically found the hunk-based approach of git autofixup to work more reliably. I use it via magit. Paired with rebase --update-refs, it's particularly helpful to automatically fixup stacked branches.
4.
by dawg 8y ago
This approach is taken by https://github.com/dlang-community/drepl and https://docs.scala-lang.org/overviews/repl/overview.html . While it works surprisingly well, you need to parse and transf
5.
by dawg 8y ago
Installer and binaries have been signed and submitted to Microsoft since a while to fix the issue with Windows Defender. https://dlang.org/changelog/2.082.0.html#signed_windows_bina... Neither the last release nor the
6.
by dawg 8y ago
Dmd releases have been signed and submitted to Microsoft since 2.082.0 to fix the issue with Windows Defender. https://dlang.org/changelog/2.082.0.html#signed_windows_bina...
7.
by dawg 9y ago
And this short snippet in D T max(T)(T a, T b) { return a < b ? b : a; } without requiring explicit constexpr annotations and with less noisy template syntax ;).
8.
by dawg 9y ago
For emacs it might be OK, usually mutating objects in the heap during marking is not a good idea, as it breaks sharing CoW pages with forks.
9.
by dawg 9y ago
Did sth. similar a while ago for our not so great D GC. https://github.com/dlang/druntime/pull/1073
10.
by dawg 9y ago
You loose builtin arrays and hashes and need to use a container library instead. Same goes for newing aggegates which can be replaced with smart pointers. Escaping closures (delegates) no longer works, but you can explicitly capture context
11.
by dawg 9y ago
You don't have to restrict yourself to betterC to use manual memory management. BetterC is mainly targetted at embedded programming and to port components of existing C applications. Malloc vs. GC vs. stdx-allocator is a separate topic
12.
by dawg 9y ago
In D which has CTFE support since ages, you'd debug such functions by invoking them at runtime. https://tour.dlang.org/tour/en/gems/compile-time-function-ev... There are also tools to print values at com
13.
by dawg 9y ago
Yes, if you're willing to spent some effort on it. Somewhat simpler you can just avoid most GC allocations so you don't run into any performance issues with the GC. http://dlang.org/blog/the-gc-series/ M
14.
by dawg 9y ago
The D language is currently heading towards deterministic and safe memory management, making it possible to avoid the GC overall, hence further work on GC improvements was deprioritized. http://dlang.org/blog/2017/
15.
by dawg 9y ago
Here is the archive.org link (requires an account) https://archive.org/details/LundukeHourApril14RMS .