firesloth

7 ms·

1.
by firesloth 2y ago
Maybe. First, you need the module name primarily for disambiguation for compiler or possibly for readability. I wouldn't recommend requiring it for everything, eg one of the arguments against requiring naming all imported symbols expli
2.
by firesloth 2y ago
It could be preserved if specifying the namespace used a different syntax. Right now, if I have the `foo` module and `bar` function, I can call `arg1.bar()`, or `foo.bar(arg1)`. But if the namespace didn't also use `.`, then it wouldn&
3.
by firesloth 3y ago
Typing that out is making me re-evaluate my position. I made my judgement a few years ago, when the technical bus factor might have legitimately been 1, but there are a lot more people involved now, and some of them may have sufficient moti
4.
by firesloth 3y ago
I believe it, but I'd be happy to be wrong. Here is my reasoning: My concern is leadership, not technical ability per se. There are a number of people capable of maintaining Nim or advancing it (off the top of my head I can think of 6)
5.
by firesloth 3y ago
Charitably reading his comment, I think he sees questions about a "foundation", "organization", etc as the thin edge of a wedge for people with political agendas. As a response to "Is there a Nim foundation?" i
6.
by firesloth 3y ago
I was under the impression that using "nimrod" as an insult was an American thing (reference https://en.wikipedia.org/wiki/Nimrod#Idiom ). The creator of Nim is European.
7.
by firesloth 4y ago
It doesn't? https://nim-lang.org/docs/re.html and https://nim-lang.org/docs/net.html are part of nim's standard library. Are they missing something you expect?
8.
by firesloth 4y ago
Has anyone tried prologue? https://github.com/planety/prologue
9.
by firesloth 4y ago
Without knowing too much about the original poster's particular circumstances, I expect this is probably the answer. If you can endure until early next year, things may improve.
10.
by firesloth 4y ago
I mentioned elsewhere, but I made a simple bash function that does something like that but matches a string in a previous commit message (because I found that easier to type quickly than a commit hash): function git-commit-fixup() {
11.
by firesloth 4y ago
Haha, true! On the other hand, is that better or worse than running into a string of "wip" commits that had the code in a broken state.
12.
by firesloth 4y ago
I've been recommending making a git tag before rebasing. eg: git tag -f pre-rebase
13.
by firesloth 4y ago
Me too. I made an alias that was _shorter_ than --force to make it easier to type (and hence more likely for me to use by default).
14.
by firesloth 4y ago
I did something very similar with a bash function: function git-commit-fixup() { git commit --fixup ":/$*" } alias gcf="git-commit-fixup" # Looks for the most recent commit that matches its arg # eg:
15.
by firesloth 4y ago
My understanding is that nim's arc memory management strategy inserts frees where it can automatically without being a GC, and that rust actually does something similar in many cases. Nim's arc doesn't handle cycles, and ther
16.
by firesloth 4y ago
I have a bash function I use to checkout a git branch based on a search string: function git-checkout-branch-by-search-string() { local maybe_branch_name maybe_branch_name=$(git branch --sort=-committerdate | grep $1 | head -n 1
17.
by firesloth 4y ago
I did something similar in bash using cd instead of jump. export CDPATH=.:~/.marks/ function mark { ln -sv "$(pwd)" ~/.marks/"$1" } I prefix all the "marks" with a symbol (eg
18.
by firesloth 4y ago
Actually another way to do nimscript is to make a config.nims file with tasks in it. eg: In config.nims: switch("hints", "off") task hello, "say hello world": echo "hello world" In bash
19.
by firesloth 4y ago
For nim, you could use something like nimcr ( https://nimble.directory/pkg/nimcr ). You put a shebang in your script `#!/usr/bin/env nimcr` and then call it like a normal script. eg: $ code script.nim