7;re not annoying 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
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.
The
SEAN
An Architect'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 dataf
really don’t understand what is the point of `nav`.
kind regards,
Dimitris
*From: *Sean Corfield <mailto:s...@corfield.org>
*Sent: *02 February 2020 07:36
*To: *Clojure Mailing List
/
>>>>
>>>>
>>>> On Sun, Feb 2, 2020 at 1:22 AM Dimitrios Jim Piliouras <
>>>> jimpil1...@gmail.com> wrote:
>>>>
>>>>> Hi Sean,
>>>>>
>>>>>
>>>>>
>>>>> Admitted
Dimitris
*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
>
>>>>
>>>> In particular I’m struggling to understand 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
Dimitris
*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 very cool but I would strongly reco
ng pattern as the last arg to nav. But again, :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
&
e 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
&
ted 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: A
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.
14 matches
Mail list logo