Idea: Only treat objects without prototypes as StrMaps

[Avaq]

Idea: Only treat objects without prototypes as StrMaps

[dotnetCarpenter]

This definitely need a StrMap ({...props}) constructor. It is already cumbersome to work with other libraries and being even stricter will not make it less cumbersome. However, if this makes the code base leaner and improve error messages, I am all for it.

But please make it simple to convert a foreign object to a StrMap.

[davidchambers]

I like this idea!

How would we describe the type of the data constructor?

StrMap :: ??? -> StrMap a

Would S.StrMap ({x: 'abc', y: 123}) throw an exception when evaluated?

[dotnetCarpenter]

I vote for a way to convert all properties to String but S.Left in the normal case. My thinking is that this might be wrong input that I need to handle but when I have made certain it is not, let me get a StrMap String.

You often get a foreign object such as:

{
  fill: '#f06'
, 'fill-opacity': 0.5
, stroke: '#000'
, 'stroke-width': 10
}

[davidchambers]

@dotnetCarpenter, are you suggesting that the data constructor's return type should be Either String (StrMap a) or Either Error (StrMap a) rather than StrMap a?

[Avaq]

Would S.StrMap ({x: 'abc', y: 123}) throw an exception when evaluated?

It might be fine just to have it return a mixed-type StrMap. It's possible to work with mixed-type StrMaps outside of Sanctuary, or using S.unchecked.

[Avaq]

It's just like the Array constructor; We allow users to do ['abc', 123], but then it's checked for consistency when this value is passed into a Sanctuary function.