Is purescript-maps deprecated?

121 views
Skip to first unread message

rvdalen

unread,
May 25, 2018, 5:44:44 AM5/25/18
to purescript
Hi everyone,

It looks like the purescript-maps package is deprecated?

I am using this package a lot.  If it is deprecated, what is the replacement?

Regards
--Rouan

Christoph Hegemann

unread,
May 25, 2018, 6:33:30 AM5/25/18
to purescript
purescript-maps has been merged with sets into https://github.com/purescript/purescript-ordered-collections

That package only works with compiler version 0.12 though, so you should continue to use purescript-maps until you've upgraded (Wait a few weeks before attempting that, the ecosystem is still catching up)

rvdalen

unread,
May 26, 2018, 4:47:27 AM5/26/18
to purescript
I will stick with purescript-maps for now.

I had a look at the purescript-ordered-collections repo, but there I could not find a StrMap type in there.
What type should we use as an equivalent of StrMap?

I make use of the fact that the runtime representation of StrMap is just a plain javascript object.  Is this still true for the Map type?

Regards
--Rouan

Christoph Hegemann

unread,
May 28, 2018, 1:45:16 PM5/28/18
to purescript
Right, StrMap has been moved into the purescript-foreign-object library under Foreign.Object.


As you already said its primary usage is in combination with the FFI, so we felt it was more appropriate to move it.

Greetings,
Christoph

rvdalen

unread,
May 29, 2018, 10:47:57 AM5/29/18
to purescript
Thanks Christoph,

I have changed most of my code to the new packages and names.
Can you maybe shed some more light on my other question regarding 'Eff' vs 'Effect'?

Will Eff be removed or can I safely use it, knowing it is here to stay?

Regards
--Rouan

Christoph Hegemann

unread,
May 30, 2018, 9:57:00 AM5/30/18
to purescript
We (the core maintainers) won't continue to maintain the purescript-eff library. You can totally fork https://github.com/purescript/purescript-eff, update it for 0.12 and continue to use it, but the path of least resistance will definitely be to move to Effect instead.

Christoph Hegemann

unread,
May 30, 2018, 9:57:51 AM5/30/18
to purescript
Fwiw, updating code from purescript-eff to purescript-effect primarily involves removing effect rows and updating imports. The runtime representation is the same for both, so you don't need to touch any FFI code.

rvdalen

unread,
May 31, 2018, 1:34:48 AM5/31/18
to purescript
Thanks Christoph

I have already switched over my code to use `Effect`.
So for myself and future readers, it seems that we should not be using `Eff` any more?
Even though it still exists.

Regards
--Rouan

Reply all
Reply to author
Forward
0 new messages