10 Commits

Author	SHA1	Message	Date
Alain Emilia Anna Zscheile	ba41ff6837	refactor: get rid of unnecessary bounds on struct generics	2024-12-12 16:38:26 +01:00
Alain Emilia Anna Zscheile	9e0bdb5bc7	refactor: various further refactorings (#128) ... These optimize out unnecessary code duplication, reserve vector capacity beforehand by leveraging `Iterator`s and avoid unnecessary double-lookups into HashMaps. Reviewed-on: https://codeberg.org/topola/topola/pulls/128 Co-authored-by: Alain Emilia Anna Zscheile <fogti+devel@ytrizja.de> Co-committed-by: Alain Emilia Anna Zscheile <fogti+devel@ytrizja.de>	2024-12-11 14:13:21 +00:00
Alain Emilia Anna Zscheile	5a26c02b4e	refactor(ApplyGeometryEdit): make 'apply' take 'GeometryEdit' by reference	2024-12-08 16:20:05 +00:00
Alain Emilia Anna Zscheile	27a4b61c4d	refactor(topola): get rid of unnecessary clones and lookups	2024-12-08 16:20:05 +00:00
Alain Emilia Anna Zscheile	0fe23c9c71	build: put `specctra` module into separate crate	2024-12-06 14:38:00 +01:00
hakki	5f6045a758	Board: added docs	2024-10-04 20:23:06 +02:00
Mikolaj Wielgus	19a4766cb5	board,dsn: introduce `MesadataTrait`, an extension of `RulesTrait` ... The trait's contents aren't implemented yet. "mesa" is supposed to mean the opposite of "meta". By "mesadata" I don't mean mere content or payload: I mean data that is stored *inside* or *under* such content or payload. I found this meaning of "mesa" -- as opposite of "meta" -- by browsing somewhere on the internet. Fair chance many classicists would think poorly of this usage. But I don't care about etymology: I just need a word to close a lexical gap.	2024-06-08 16:36:21 +02:00
Mikolaj Wielgus	1dc3718159	board: move board to its own directory	2024-06-08 13:37:27 +02:00
Mikolaj Wielgus	ef823c1c27	board,layout: rename "layout" to "drawing", "board" to "layout"	2024-03-22 23:23:31 +00:00
Mikolaj Wielgus	2f6b40410c	board: make layout private ... Also add board/ directory, as I forgot to add it in the previous commit.	2024-02-29 02:28:15 +00:00