Morning.

UK specific thing: So I see there are lots of houses with conservatories. Are they usable all year?

My mum's is, yes. No matter what time of year we visit, we pretty much always sit out in the conservatory to drink our morning coffee/tea and read the papers.

She usually tries to get us to sit at the dining table for breakfast but if we get to the kitchen first, we make our own breakfast and go eat that in the conservatory. Mid-afternoon we'll usually go and after tea and snacks in the conservatory as well.

¡månmån!

Morning!

Ours gets very hot in the summer, and very cold in the winter (and loud in the rain). Mostly it's just used for storing toys

morning

ours is the warmest room in the house most times of year

but we had it fully boarded out and sealed under the eaves

Thanks. And would you build one if you bought a house with enough space for it?

moin moin

Morning

Our conservatory is usable all year round, although we do have two small radiators in that room. They (conservatories) are prone to leaks over time. If I had a choice, I'd spend the extra to do a proper extension with skylights. If that isn't an option, I'd recommend putting a light tile roof on the conservatory as it will be less prone to leaks, plus it's a bit more insulated and you can install electrical lighting, etc.

what is > a light tile room ?

It's simple, it can mount 20 - 35 tons of tiles. Medium is 40 - 55 tons, Heavy is 60 - 70 tons and Assault is up to 100 tons

haha

sorry i read conservatory as loft somehow lol

i wouldn't bother with a conservatory personally, as much for security reasons as anything

I think I've found a new language to upsurp Clojure...

Thank you all. So it seems to me that there are all kinds of opinions to conservatory usability & viability. 🙂

My brother just had his refitted; he lives up north and it does give a nice warm area to sit in spring / autumn, and somewhere to work in summer that's almost the garden but has nice seating and power and no risk of passing pigeons decorating your laptop screen from on high.

@jiriknesl: if you want something more substantial than a conservatory, a bit more pretentious, but better insulated and most likely more expensive, then at that extreme you’re looking at an orangery.

I got a letter through the door with important information about "my" conservatory (I don't own one). Informing me that laws have changed, and you don't need a transparent roof anymore that lets all the heat out.

Morn' 😃...

@rickmoynihan thank you, I was looking at orangeries too. I am looking for a place where we can eat & sit and have more sunlight (I badly miss sunlight here in the UK)

Wow, not thought about conservatories in ages, I used to have one growing up, but we rarely sat in it so I've not really thought about it...

anyone got any examples of deliberate variable capture in a macro, which they consider to be a good solution ?

(i've got a macro problem and i'm struggling to find a solution that doesn't involve a deliberate variable capture... so wondering whether i should go with it or keep looking)

I guess the usual examples would be anaphoric macros like those discussed in Let Over Lambda, where you're deliberately capturing a variable like 'self' or 'it' or 'this'

Whether that's nice or not depends on what you're doing 😉

it is for a similar use-case to self... i'd forgotten the name "anaphoric" - thanks @clarkema

next question ... are there any conventions for naming anaphors in clojure ?

ah, there's a bit on it here: https://livebook.manning.com/book/the-joy-of-clojure/chapter-8/147

That's interesting reading, thanks. I haven't seen it used much in Clojure; the examples in LoL and On Lisp are called things like alambda and aif, which I'm not really a fan of. They feel a bit clumsy, don't tell you what's going on unless you already know, and lead to a profusion of different XYZlambda variants that macro different combinations of features on top of the basic lambda

i've got a case which is kinda like the this in proxy mentioned in t.j.o.c ... it's to capture the context being used for a chain of monadic computations, and can then be used by a bunch of helper macros to eliminate a lot of boilerplate - i think it works out quite nicely, just need to choose a name which is unlikely to accidentally clash with user bindings

the-thingy

Is it intended to be visible to the user to allow them to hook into the computation, or is it for private context communication between nested macros?

generally the latter

i think i'm going to go with a ## suffix, after the style of gensyms... so something like this-monad##

No way of avoiding it with the threading macros?

no... not that i can see

works quite well, i think: https://github.com/mccraigmccraig/laters/blob/master/src/laters/control/state.cljc#L54

I thought your library was named lasers, and I wanted to play with it immediately. I'm now less impressed.

i am the worst library-namer in the world @dominicm

1 character short. You're getting better.