| 19 Feb 2023 |
@ronnypfannschmidt:matrix.org | In reply to @infinisil:matrix.org Ronny: An option type for that already exists, attrsOf package. The bigger issue is backwards compatibility and maybe a way to still use lists but have them be coerced to an attribute set i specifically meant a option type that will allow both lists and attrsets and coerce them into lists, for merge
my understanding is that same name packages in different sets are possible when they dont actually conflict
| 13:25:21 |
infinisil | Ronny: Coercing to a list won't have any of the benefits of attribute sets though | 13:26:32 |
infinisil | One of the main ones being the ability to remove a package | 13:26:57 |
@ronnypfannschmidt:matrix.org | removal is currently not possible anyway as far as i understood
imho a good starting point is to etablish using attr sets early and as default so people can migrate to using the better syntax
and once the majority o usages are changed its time to enable extra features
nontheless it seems potentially terrifying if other modules are allowed to remove packages of the sets | 13:30:02 |
infinisil | Ronny: If we can coerce from lists to attribute sets there will be no need for attribute set syntax though, while still getting the benetifs of attribute sets. And the implementation can indeed work by using either the package name as an attribute name, or using the attribute path to the package (a bit harder) | 13:40:34 |
infinisil | In reply to @ronnypfannschmidt:matrix.org removal is currently not possible anyway as far as i understood
imho a good starting point is to etablish using attr sets early and as default so people can migrate to using the better syntax
and once the majority o usages are changed its time to enable extra features
nontheless it seems potentially terrifying if other modules are allowed to remove packages of the sets This is already the case though, all modules can do anything to the system id they want to, they all have root access so to speak | 13:41:28 |
infinisil | In reply to @ronnypfannschmidt:matrix.org removal is currently not possible anyway as far as i understood
imho a good starting point is to etablish using attr sets early and as default so people can migrate to using the better syntax
and once the majority o usages are changed its time to enable extra features
nontheless it seems potentially terrifying if other modules are allowed to remove packages of the sets * Regardjng allowing modules tk remove options: This is already the case though, all modules can do anything to the system id they want to, they all have root access so to speak | 13:42:22 |
infinisil | (Damn, made a lot of typos on my phone in the train, but the matrix client somehow doesn't let me edit multiple times) | 13:44:24 |