to meet people. (And they also have a full bar.)
-austin
--
Austin Haas
Pet Tomato, Inc.
http://pettomato.com
On Wed Feb 06 20:27 , Alex Miller wrote:
Clojure/West has a great schedule lined up. If you haven't yet, check out
the schedule at http://clojurewest.org/schedule. You can register
Hi Brian,
You should post your question to the miniKanren Google group.
minikan...@googlegroups.com
-austin
--
Austin Haas
Pet Tomato, Inc.
http://pettomato.com
On Sat May 25 10:21 , Brian Craft wrote:
Wondering if anyone can give me some pointers with this, as I dive into
logic
://github.com/clojure/core.logic/blob/master/src/main/clojure/clojure/core/logic.clj#L1581
I must be missing something. Any pointers would be appreciated.
-austin
--
Austin Haas
Pet Tomato, Inc.
http://pettomato.com
--
You received this message because you are subscribed to the Google
Groups Clojure
--
Austin Haas
Pet Tomato, Inc.
http://pettomato.com
On Tue Jan 08 07:28 , David Nolen wrote:
The dispatching mechanism was more trouble than it was worth but we did
lose some flexibility. Do you really need to unify Sequential or is
unifying with a concrete type like PersistentVector work well
implementation?
-austin
--
Austin Haas
Pet Tomato, Inc.
http://pettomato.com
On Tue Jan 08 14:30 , David Nolen wrote:
I've updated the experimental core.logic Datomic support so that you can
unify PersistentVector and Datoms again. In a real system I'd probably
recommend providing your own tuple type
I'm having trouble isolating a small test case. I call the following code
in an update tick:
(let [prev' @prev
state' @state]
(let [rems (clojure.set/difference prev' state')
adds (clojure.set/difference state' prev')]
(reset! prev state')
(assert (= (count rems) (count
how
sets and hashing are implemented.)
I'll keep debugging.
- austin
On Tuesday, May 20, 2014 8:36:37 AM UTC-7, David Nolen wrote:
Can you demonstrate a complete minimal example?
Thanks,
David
On Tue, May 20, 2014 at 4:06 AM, Austin Haas
aus...@pettomato.comjavascript:
wrote:
I'm
This is great, David!
Is it difficult to include dependencies (e.g., core.async) for a project built
this way?
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new
I have the same problem: I need to log warnings based on some criteria and
reject records completely based on other criteria. I'm currently using two
separate specs, but I haven't convinced myself that is the best solution.
--
You received this message because you are subscribed to the Google
I don't want to use a package manager with Emacs.
Should I launch a REPL outside of Emacs, then connect to it? Using the CLI
tools (i.e., from the command line: clojure -J-Dclojure.server.repl="{:port
:accept clojure.core.server/repl}")?
Can I launch a REPL from within Emacs?
I've been
I tried Monroe, yesterday. It seems to work as advertised. I didn't have
any issues. It's nice that "jump to definition" works out of the box. It
does not appear to support Eldoc, so no help with function signatures.
This is the Emacs config I'm currently using:
;;; clojure-mode
t
>> Cider, just a statement of fact that Cider's support for ClojureScript
>> development has so far been lacking, IME)
>>
>>
>> On Thursday, July 5, 2018 at 10:51:02 AM UTC-7, Austin Haas wrote:
>>>
>>>
>>> I tried Monroe, yesterday. It seems to
This is good, relevant information. Thank you, Andrea.
On Thursday, July 5, 2018 at 4:32:58 PM UTC-7, Andrea Richiardi wrote:
>
>
>
> On Thursday, July 5, 2018 at 1:01:14 PM UTC-7, Austin Haas wrote:
>>
>> Gary, I had tried Figwheel a couple years ago and I had a pos
I spent a couple more hours working with Monroe and Figwheel. I still can't
figure out how to use the REPL. After trying to evaluate a few expressions,
Emacs gets completely locked up spewing the following error message 1000s
of times:
clojure.lang.ExceptionInfo: Arguments to require must be
I shouldn't have said that two of those errors were the same. They're
different, but they both mention unquoted symbols.
Monroe
clojure.lang.ExceptionInfo: Arguments to require must be quoted. Offending
spec: (symbol (namespace (quote clojure.repl/pst))) at line 1
{:file "", :line 1,
I've determined that the previously mentioned errors are related to
incompatibilities with inf-clojure and clojurescript.
I filed a bug, and a workaround, with inf-clojure
here: https://github.com/clojure-emacs/inf-clojure/issues/150
--
You received this message because you are subscribed to
Yesterday, I followed the excellent "Clojurescript Quick Start Guide"
(https://clojurescript.org/guides/quick-start). Everything worked as
expected. They did a great job of making it as minimal as possible.
After that, I followed the "Emacs and Inferior Clojure Interaction Mode"
guide
cljs-canary -m cljs.main -re node -r
>
> You need the right deps.edn aliases - then you will be able to nc
> localhost or inf-clojure-connect to it.
>
> On Friday, July 6, 2018 at 11:18:56 AM UTC-7, Austin Haas wrote:
>>
>> I spent a couple more hours working wi
Quick update.
After a reboot, my REPL starts up much faster (~3-4 seconds) than I
reported above. Sorry for the noise.
I started adding CLJS support to inf-clojure:
https://github.com/austinhaas/inf-clojure/tree/cljs Some of the problems
that I reported above were due to inf-clojure only
Thanks for the replies.
I only want a stable REPL, integrated with Emacs, and nothing else.
Łukasz, why did you switch to Monroe? What do you prefer about it?
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to
I don't understand what is going on here. I'm trying to throw an exception
with a cause and sometimes the cause is included in the stacktrace and
sometimes it isn't.
~$ clj -Sdeps '{:deps {org.clojure/clojure {:mvn/version "1.10.0-beta4"}}}'
Clojure 1.10.0-beta4
user=> (try (/ 1 0) (catch
ized) repl machinery out of the picture.
>
>
>
>
>
>
> On Wednesday, October 24, 2018 at 8:52:58 PM UTC-5, Austin Haas wrote:
>>
>> I don't understand what is going on here. I'm trying to throw an
>> exception with a cause and sometimes the cause is inc
ommand line options by default, for faster startup
> times I think, that might affect how much detail is captured in stack
> traces when exceptions are created.
>
> Andy
>
> On Wed, Oct 24, 2018 at 6:53 PM Austin Haas > wrote:
>
>> I don't understand what is going
"Several tools already exist to AOT compile deps.edn projects."
Alex, can you please identify some of those projects? I haven't been able
to find any.
-austin
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to
I have to use AOT for a project, because it uses Apache Beam/Google
Dataflow.
There are two libraries: A and B. A depends on B. Both require AOT.
B uses :aot :all in the project.clj :dev profile, so that it will AOT for
tests, but not for the jar.
A uses :aot :all at the top level of its
Thanks for your replies.
I've looked at clj-headlights a bunch, and datasplash, too. I was mistaken
to think that AOT was necessary. Earlier in the project, AOT simplified a
few things, like affording the use of anonymous functions (in ParDo
implementations), and I don't think I realized
We ended up sticking with AOT (for now, anyway), because it seems easier to
manage in the codebase. The alternative is to use data structures that can
be eval'd, like you would use in the body of a macro. I like how that
clearly separates the code that runs on the local machine from that which
mit)))
>
> (looks-finite? (map inc (range))) ;; => false
> (looks-finite? (map inc (range 100))) ;; => true
>
> I hope that helps.
>
> Juan
> El domingo, 1 de noviembre de 2020 a las 20:06:39 UTC-3, Austin Haas
> escribió:
>
>>
>> How can
gt; > realizing the input, as it relies on the hash, which relies on the
> > fully realized value
> >
> > On Mon, Nov 2, 2020 at 12:32 PM Austin Haas
> wrote:
> > >
> > > Thanks, Juan.
> > >
> > > I don't need to know the length of the se
How can I make sure that a logging function won't try to realize an
infinite lazy seq that could be anywhere in the arguments passed to the
logging function?
Is there some way to guarantee that lazy seqs won't be realized when
converting to a string?
I know I can bind *print-length*, but I
gt; ~file "line:" ~line
> "on thread:"
> (.getName (Thread/currentThread
>
>
> On Sat, Jan 2, 2021 at 5:59 PM Austin Haas wrote:
>
>> Ah, thanks for pointing that out. I must've overlooked your example,
>> because I'd already written off f
or runWorker
> ThreadPoolExecutor.java 1128]
> [java.util.concurrent.ThreadPoolExecutor$Worker run
> ThreadPoolExecutor.java 628]
> [java.lang.Thread run Thread.java 834]]}
>
>
>
> On Thu, Dec 31, 2020 at 1:48 PM Austin Haas wrote:
>
>>
>> Problem: When I con
deref
>
> good luck finding your solution
>
> On Sat, Jan 2, 2021 at 12:50 PM Austin Haas wrote:
>
>> Thank you very much for the explanation, Justin.
>>
>> I don't see how I can use futures, though, without blocking on the main
>> thread (to get the exception
Problem: When I connect to a socket server and create a thread, exceptions
in the thread are printed in the server's process, not the client's. I'd
like them to appear in the client's process, where the thread was created.
(I'm using the term "process" very generally here, because I don't
34 matches
Mail list logo
