This doesn't seem bb specific, might as well post in #C03S1KBA2 or #C053PTJE6 or so

Welcome to discuss here too of course

True, good point!

I would love to know the answer to this. I moved to using tap> but this still clutters the functions.

I usually do it as written above, but usually don't write to stdout, as this may mess with tools that read output.

(binding [*out* *err*] ...)

tap> is for debugging I would say, not for "production" error messages

But with tap you can separate out the result of the tap without changing the running program by defining the tap you want to use. SO I think it might make sense in production

if you control who calls add-tap, but this isn't true for library code

I agree. As a subject the idea of logging being a side effect is an issue for so called pure functions.

to make the function pure you could return {:errors [..] :result ..} but then you would have to handle those errors somewhere

That is a useful thought. it is easy to forget that we can return structure results in that way. Some languages allow multiple return values to replicate this.

I’m in the habit of printing info-level stuff to the end user of my script, but perhaps that's too much. I suppose I could limit my printing to errors when something goes wrong. That would reduce the number of prints.

Its almost like an option to switch on tracing somewhat like the +X for bash scripts would be good. Or the equivalent of the AOT in bb at script runtime.

you could also pass in a function to invoke for status/logging. Like tap>, but the caller specifies the function. If the passed in arg is nil don't call it.

@UKH2HDSQH Does Clojure cope calling nil as a function with arguments? Otherwise you would have to include lots of if's or when's

no it doesn't. but you can default to identity or some other function that does nothing

you would need to boilerplate that away somehow. You could be lazy and make identity the default for the arg, but you might want another function or macro that puts in the boilerplate

Does SCI do any runtime optimizations?

(`fnil` is another function that can help with handling nils)

@U4C3ZU6KX what exactly do you mean?

The issue with having lots of conditionals is that they will cost time, so if you included a macro that expanded to cond and if the first conditional was say the nil function so that you could see that when nil is passed in the SCI would see that it results in no code and so it could remove the cond altogether.

it actually does something like this for if yes

it's not a runtime optimization but a "compile" time optimization

Great, I thought you would have thought of that !

https://github.com/babashka/sci/blob/e9fca84a40d975c276717088136bf4c996f9c506/src/sci/impl/analyzer.cljc#L862

so when you write (if nil 1 2) it will actually only ever run "2"

I guess another optimization would have been possible for the reverse: (if :else 1 2) could expand directly into 1

oh it already does that too: https://github.com/babashka/sci/blob/e9fca84a40d975c276717088136bf4c996f9c506/src/sci/impl/analyzer.cljc#L854

🙂

Would this work with the executable bundle? I am assuming it would as you bundle bb into the the package so the script is still compiled on the fly.

yes, it works exactly the same

Are you following redirects? That would be my first guess. Second, some services will block unknown user agents and deny traffic. Lastly, some images might be accessible only when you're authenticated.

I don’t think it’s that, because the files are very similar. I suspect it’s an encoding issue, because the real file has weird block characters in Emacs, and the babashka downloaded one has control sequences, like \357

Yeah, spit isn’t preserving something, if I slurp/spit the real file, I get the contents of the downloaded one.

you aren't using slurp are you? this is for text, not binary data

use babashka.http-client + :as :bytes to download binary data

I’m using http/get

ah ha

https://github.com/babashka/http-client?tab=readme-ov-file#download-binary

also don't use spit for binary data

I’m using fs/write-bytes

👍

Amazing, that worked!

Thanks so much

👍