Fork me on GitHub
#clojure-europe
<
2020-09-11
>
slipset06:09:05

@raymcdermott what would you use read+string for?

genRaiy06:09:43

to ensure embedded forms in strings are readable and retain the original input embedded string

slipset06:09:26

Oh, yeah, god morgen!

slipset06:09:20

Right, because with a normal read you loose the input string.

genRaiy06:09:04

:thumbsup::skin-tone-3:

genRaiy06:09:08

obvs if you can read the whole string, there is no added value - it's only good for many forms in one string

borkdude13:09:21

good morning y'all

synthomat13:09:50

good morning!

otfrom13:09:59

more fun with x/by-key today, and indeed x/reduce. I'm going reduces in by by key reduces because I heard you liked yo dawgs or something

😂 3
dominicm17:09:35

Sounds like my future. I have some fun plans with transducers and SQL. Suddenly I can test something useful around SQL because I have transducers for the processing aspect, and they can apply backpressure to the chunking. It's amazing.

borkdude17:09:38

We've also been doing that for a while

borkdude17:09:05

There's also support for it in java.jdbc and next.jdbc now

dominicm18:09:19

Yeah. I'm not sure if we'll migrate for this feature or not.

borkdude18:09:30

no need to migrate?

borkdude18:09:56

we've even been using this technique well before it was available in java.jdbc (not even next.jdbc).

dominicm19:09:22

Oh really, you're clearly hardcore 😀 jdbc scares me.

borkdude19:09:44

if you're not using jdbc, what are you..?

borkdude19:09:33

I mean, we were using clojure.java.jdbc, not the Java stuff directly, but even before it had explicit transducer support, it was possible (kudos to a colleague)

dominicm20:09:41

I meant using it raw :)

borkdude20:09:43

yeah, not that hardcore either ;)