You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
setAttrByPath currently takes two arguments, the key and the value, and returns a new set where the given key is set to the given value. While setAttr takes a set, key, and value, but does not allow for full paths like implied by the name of the function at hand. I think it would fit better into the attrsets module by taking a set as an argument as well so setAttrByPath : Set -> [String] -> a -> Set. setAttr can then be defined in terms of setAttrByPath, and we can also add a new function that covers the old behaviour, also defined in terms of setAttrByPath.
The text was updated successfully, but these errors were encountered:
This has been automatically marked as stale because it has had no activity for 180 days.
If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.
Here are suggestions that might help resolve this more quickly:
Search for maintainers and people that previously touched the related code and @ mention them in a comment.
Issue description
setAttrByPath
currently takes two arguments, the key and the value, and returns a new set where the given key is set to the given value. WhilesetAttr
takes a set, key, and value, but does not allow for full paths like implied by the name of the function at hand. I think it would fit better into theattrsets
module by taking a set as an argument as well sosetAttrByPath : Set -> [String] -> a -> Set
.setAttr
can then be defined in terms ofsetAttrByPath
, and we can also add a new function that covers the old behaviour, also defined in terms ofsetAttrByPath
.The text was updated successfully, but these errors were encountered: