I've rewritten JCLI, and this is the first release where I think
it's useable again: https://code.dlang.org/packages/jcli
Here's a snippet from the README
# Features
* Building:
* This library was primarily built using
[Meson](https://mesonbuild.com) as the build system, so should be
fu
On Wednesday, 25 August 2021 at 09:18:50 UTC, SealabJaster wrote:
...
Oh, I'd also like to redocument the code. The old code was almost
50% comments or something, and the rewrite has almost no comments.
Thank you all for the warm welcome!
---
On Wednesday, 25 August 2021 at 06:11:04 UTC, Vladimir Panteleev
wrote:
Cool! How does it compare to the `trash` command from the
`trash-cli` package?
To quote the `trash-cli` README
Although the interface of trash-put seems to be compatible with
rm,
On Wednesday, 25 August 2021 at 06:23:37 UTC, Kagamin wrote:
You marked all functions inline?
If I did then it wasn't on purpose, I was only trying to mark the
handful of helper functions as inline. If you know a solution to
this, that would be greatly appreciated!
On Wednesday, 25 August 2021 at 13:30:58 UTC, rushsteve1 wrote:
On Wednesday, 25 August 2021 at 06:23:37 UTC, Kagamin wrote:
You marked all functions inline?
If I did then it wasn't on purpose, I was only trying to mark
the handful of helper functions as inline. If you know a
solution to thi
On Wednesday, 25 August 2021 at 13:52:32 UTC, Paul Backus wrote:
To be honest, you could probably remove `pragma(inline)` from
the program altogether and not notice a difference. A program
like this is almost certainly going to be bottlenecked on IO
long before function-call overhead makes a no
On Wednesday, 25 August 2021 at 13:30:36 UTC, rushsteve1 wrote:
`trash-d` tries to mimic `rm`'s semantics as much as possible.
It also unifies all the different `trash-*` commands that
`trash-cli` provides into a single one with flags. One of my
goals with `trash-d` was to make a simpler and sm
On Wednesday, 25 August 2021 at 18:37:33 UTC, Vladimir Panteleev
wrote:
I suggest investigating that as a future improvement. Not only
is moving files within the same volume much faster (potentially
an O(1) operation as opposed to having to read then write every
byte of data), but it can also r
