Fork me on GitHub
#clojure-uk
<
2017-04-24
>
peterwestmacott06:04:20

rcfotd:

-------------------------
clojure.core/await
([& agents])
  Blocks the current thread (indefinitely!) until all actions
  dispatched thus far, from this thread or agent, to the agent(s) have
  occurred.  Will block on failed agents.  Will never return if
  a failed agent is restarted with :clear-actions true.

agile_geek07:04:00

Hmm, never used it, probably never will.

mccraigmccraig07:04:38

cor, agents, haven't used them in a while... i used them once in an async twitter api client, but i think i would use promises & streams now

thomas08:04:05

await reads like a rather risky function.

dominicm08:04:11

It's a bit strange to me: I mostly write webapp-y server-side applications, which means I don't touch var containers at all. I have used them extensively in one application, but I don't see me working on that much 🙂

danp08:04:39

Morning all - coincidentally, I actually read about await this morning in Joy of Clojure, which I'm reading through. From reading all your comments, maybe I'll just skip to the next chapter 🙂

maleghast08:04:24

Morning All 🙂

thomas09:04:42

@danp maybe read it anyway... and then tell us why we are wrong/right 😉

danp09:04:01

haha @thomas - I didn't say I understood any of it!

thomas09:04:39

@danp neither do I... but I just read the description and the fact that it can block for ever is (almost) a good enough reason for me to try and not use it.

thomas09:04:15

then again.... it might have a lot of value in some arcane case that I am not aware of.

danp09:04:46

true true, all I could think of when reading was "I'll probably never need this, but should read it for completion's sake" 😄

dotemacs10:04:13

@agile_geek everyone wants to be you right now! 🙂

agile_geek10:04:08

@dotemacs no they don't. I am in that horrible situation where you've spent ages proving the bug doesn't exist but the biz users insists it does exist

agile_geek10:04:10

Wish I could but first I have to prove a negative!

mccraigmccraig10:04:22

there you go with your virtuous behaviour making life difficult for yourself!

peterwestmacott10:04:18

isn’t the onus on them to provide a reproducible test case?

minimal10:04:00

submit a placebo fix

peterwestmacott10:04:00

I wasn’t actually joking. Perhaps I’ve been spoiled.

mccraigmccraig10:04:45

s/#clojure-uk/#pragmaticdev-top-tips/

mccraigmccraig11:04:32

more seriously, get a bizuser to do a screencap vid showing the bug in action

thomas11:04:24

@mccraigmccraig that is what our customers tend to do. a screencap of the bug in action is very helpful indeed.

dominicm13:04:03

Similar string of thoughts: Do you guys have separate "issue" lists for biz users & technical? The Biz users being high level requirements which allows them to choose importance, and then a technical board for developers to actually build it.

thomas13:04:58

@dominicm nope. just one Jira board for both.

thomas13:04:55

and as both biz users and tech users are stakeholders they should have an insight into what is the over all priority IMHO

iecya14:04:23

Hello everyone, I am reaching out to let you know about the next ClojureBridge event on 2nd and 3rd June in London. For those who doesn't know already, ClojureBridge is a initiative whose goal is to increase diversity in the technology community through workshops. The event is aimed mainly to women and all the minorities in Tech and teaches the Clojure programming language to everyone who attend. For finding out more and attend the workshop please visit our website at https://clojurebridgelondon.github.io/ Also, feel free to direct message me for any further question or share with anyone you know might be interested