Named layers in parsing cluster syntax #5

New issue

Open

opened 2026-02-15 16:44:40 +00:00 by UserCurt · 0 comments

UserCurt commented

2026-02-15 16:44:40 +00:00

(Migrated from codeberg.org)

Currently, the cluster selection syntax supports selecting layers using LAYER-0, LAYER-1, etc. It can be helpful for users if allowing selection of layers as named layers. This feature request is for adding support for this.

The simplest way would be to use the name of the layer, so SHIFT_LAYER for example. The only risk here is with overlaps (which can be addressed through the prefix =). This approach does mean the keywords are dynamics, and whether there are conflicts is dependent on what layout is selected. This can be surprising if using the same constraints file across different layouts.

Alternative option include mandating surrounding with <...> (or having < and > not part of the layer name), or using some other surrounding syntax, though this could require using quotes in the terminal. This may be difficult to get around as most symbols can be interpreted by PowerShell.

Currently, the cluster selection syntax supports selecting layers using `LAYER-0`, `LAYER-1`, etc. It can be helpful for users if allowing selection of layers as named layers. This feature request is for adding support for this. The simplest way would be to use the name of the layer, so `SHIFT_LAYER` for example. The only risk here is with overlaps (which can be addressed through the prefix `=`). This approach does mean the keywords are dynamics, and whether there are conflicts is dependent on what layout is selected. This can be surprising if using the same constraints file across different layouts. Alternative option include mandating surrounding with `<...>` (or having `<` and `>` not part of the layer name), or using some other surrounding syntax, though this could require using quotes in the terminal. This may be difficult to get around as most symbols can be interpreted by PowerShell.