```
compile error: expected 2 element tuple for l-value to set
compile error: expected 2 element tuple for l-value to set
oh hmm, what does
(get-in wait, you're using@(instead of@[`?
so...
try put-in
Maybe i should look into making my own
++in macro
I guess it's
put and alike for associative datastructures and set for vars
hmmm, no, set works on keyed data structures per the specials doc
but yes, I sorta would have assumed
(++ (variant-amount-of-gets-here)) would have worked
Ok, this does the trick for me:
(defmacro ++in [variable arr] ~(,put-in ,variable ,arr (+ (,get-in ,variable ,arr) 1)))
I think
update-in is probably the best way to do what you want using standard pieces
1 reply
Relevant to the recurring conversation about more powerful version resolution in jpm, this is apparently all the rage: https://nex3.medium.com/pubgrub-2fb6470504f
jpm doesn't seem to have a command for updating installed jpm packages.
Reinstalling a package should update. No easy way to update all at once though besides iterating through the manifest
or even better I have 64 bit number and I need to create string with bytes from it :-)
This is the best I have managed to do it :-)
(string/from-bytes 2r01111111
;(seq [i :down-to [56 0 8]]
(scan-number (string (band (brshift (int/u64 dl) i) 0x000000FF)))))
the 64bits number is the seq
@saikyun: PS: finaly fixing trevor, as I got over the 16 bits size tooo :-)
I took a break from working on my blog, hopefully I'll get to it again sometime soon :)
2 replies
I got a new job and will work 50% on creating a game using Freja :D starting in janetuary
If one was to need a config file for software they've written, what do people typically use with Janet
I see there is support for toml and json. No idea about yaml or ini. I really dislike json for configuration files, but I have used json with Janet for talking to other processes so I know that works well. XML and alike are most definitely a no go.
I see there is support for toml and json. No idea about yaml or ini. I really dislike json for configuration files, but I have used json with Janet for talking to other processes so I know that works well. XML and alike are most definitely a no go.
very good question about which I am not sure, but it is a Janet code at the end, so I guess you can
hmmm, since it's janet code, I guess the major diff between it and regular janet code is it only allows returning values? as in, protected from arbitrary code exec?
well I am reading the config this way:
(def file-conf ((compile (parse (slurp file))))) so definitely executing the code
but I guess you can protect it easily
depending on what you want, you don't need to do
compile iiuc: https://github.com/janet-lang/janet/blob/master/test/suite0008.janet#L297-L298
Indeed. to be frank, I am not sure why I do in the snippet I have sent :-)
well I highly recommend it, especially to someone already deep in Janet as I feel you are