nnoying somebody, you're not really alive."
-- Margaret Atwood
From: dimitris
Sent: Monday, February 10, 2020 2:20 PM
To: clojure@googlegroups.com
Subject: Re: ANN: jedi-time 0.1.4
On 10/02/2020 20:45, Sean Corfield wrote:
> I’m suggesting that if you add certain key/value pairs to the d
On 10/02/2020 20:45, Sean Corfield wrote:
I’m suggesting that if you add certain key/value pairs to the datafied
Java Time values, nav could recognize those as navigation from data to
“stuff”. This gets you much closer to your original concept while
staying within the datafy/nav confines.
chitect's View -- http://corfield.org/
"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood
From: dimitris
Sent: Monday, February 10, 2020 4:50 AM
To: clojure@googlegroups.com
Subject: Re: ANN: jedi-time 0.1.4
Ok, I'm glad datafy/nav works as expected, but t
*From: *Sean Corfield <mailto:s...@corfield.org>
*Sent: *02 February 2020 07:36
*To: *Clojure Mailing List
<mailto:clojure@googlegroups.com>
*Subject: *Re: ANN: jedi-time 0.1.4
This is v
t;>>> jimpil1...@gmail.com> wrote:
>>>>
>>>>> Hi Sean,
>>>>>
>>>>>
>>>>>
>>>>> Admittedly, I’ve never used REBL, and I did struggle with the shape
>>>>> and name of the `nav` arguments...
>
*Sent: *02 February 2020 07:36
*To: *Clojure Mailing List
<mailto:clojure@googlegroups.com>
*Subject: *Re: ANN: jedi-time 0.1.4
This is very cool but I would strongly recommend you
try using this wit
rstand why would anyone use `nav`
>>>> to navigate to a key that already exists in the map...Can’t we just use
>>>> `get` or `get-in`?
>>>>
>>>> You used the :format as an example, which works with nil, :iso, or a
>>>> String pattern a
d.org>
*Sent: *02 February 2020 07:36
*To: *Clojure Mailing List <mailto:clojure@googlegroups.com>
*Subject: *Re: ANN: jedi-time 0.1.4
This is very cool but I would strongly recommend you try
using this with REBL so you can figure out h
:format is NOT in the
>>> datafied representation.
>>>
>>>
>>>
>>> In essence, I’ve tried to use `nav` to navigate to things that can be
>>> expensive and don’t necessarily belong in the actual datafied
>>> representation.
>>>
>
ent
>> in the map, then I really don’t understand what is the point of `nav`.
>>
>>
>>
>> kind regards,
>>
>> Dimitris
>>
>>
>>
>>
>>
>> *From: *Sean Corfield
>> *Sent: *02 February 2020 07:36
>> *To: *Clojur
o be a key already present
> in the map, then I really don’t understand what is the point of `nav`.
>
>
>
> kind regards,
>
> Dimitris
>
>
>
>
>
> *From: *Sean Corfield
> *Sent: *02 February 2020 07:36
> *To: *Clojure Mailing List
> *Subject: *Re: ANN: j
or converted to an alternate version?
3. Why would I ever navigate the existing keys of a map via `nav` (as opposed
to the standard functions)?
Kind regards,
Dimitris
From: Dimitrios Jim Piliouras
Sent: 02 February 2020 09:22
To: clojure@googlegroups.com
Subject: RE: ANN: jedi-time 0.1.4
Hi Sean
.
If the second argument to `nav`, is expected to be a key already present in
the map, then I really don’t understand what is the point of `nav`.
kind regards,
Dimitris
From: Sean Corfield
Sent: 02 February 2020 07:36
To: Clojure Mailing List
Subject: Re: ANN: jedi-time 0.1.4
This is very cool
This is very cool but I would strongly recommend you try using this with
REBL so you can figure out how to make the `nav` part work in a more
natural way.
nav is intended to work with a key and value (from the datafied structure),
but your nav expects special values so it doesn't work with REBL.
Hi folks,
The first public release of `jedi-time` should be hitting clojars any
minute now. I am traveling next week so may be slow to reply to
feedback/bugs/PRs...
https://github.com/jimpil/jedi-time
Kind regards,
Dimitris
--
You received this message because you are subscribed to the
15 matches
Mail list logo