I am confused about the best way to assure that I am dealing with a vector
when dealing with core library functions that often return seq where I then
lose my ability to access it using associative accesses (get-in
specifically).
My particular use case is as follows:
I am modeling a matrix as
oss and convert the output to a vector.
>
> On Thursday, May 8, 2014 7:28:47 PM UTC-4, Joseph Rollins wrote:
>>
>> I am confused about the best way to assure that I am dealing with a
>> vector when dealing with core library functions that often return seq where
>> I th
trix? m)] :post [(matrix? %)]}
> (apply mapv vector m))
>
> That'll provide some type guarantees.
>
> - James
>
>
> On 9 May 2014 00:28, Joseph Rollins >wrote:
>
>> I am confused about the best way to assure that I am dealing with a
>> vector when dealing
I'm having some trouble with what should be a trivial application of
core.async and cljs-http. I have tried to debug it, but I don't have a
great setup for properly debugging. Also, debugging core.async channels is
well above my current ability.
I've whittled the code down to the least common d
es" is a good way to detect collisions in the
meantime.
As an aside, I think I will be trying out SublimeText w/ SublimeREPL until
LightTable fixes its dependence on an increasingly old release of
clojurescript.
-Joseph
On Sunday, May 18, 2014 2:43:58 PM UTC-4, Joseph Rollins wrote:
>
&g
available in master.
>
> Best.
> Mike
> On May 18, 2014 4:15 PM, "Joseph Rollins" >
> wrote:
>
>> Managed to figure out the culprit with some help from IRC. I was
>> attempting to use cljs-http "0.1.10" with clojurescript "0.0-2173"
