RFC breaking change: removal of certain setup
options
#50
Closed
opened 4 years ago by mbutterick
·
4 comments
Loading…
Reference in New Issue
There is no content yet.
Delete Branch '%!s(<nil>)'
Deleting a branch is permanent. It CANNOT be undone. Continue?
I’d like to get rid of these user-configurable
setup
values, because I don’t believe they’re widely used (if at all), and Pollen accesses them frequently, which means a performance cost for no benefit.The result of removing these is that the default value (shown on the right) would become the permanent, immutable value. Projects that have not overridden these values would work exactly the same way.
I don't use them! but I'm curious: how big an impact do they have on performance? does Racket profiling capture this kind of thing? (I've never used
define-settable
)It produced a small improvement when I tested the change with my Pollen projects (I haven’t used the Racket profiler). But it’s not on the level of, say, parallel processing or issue #49.
I see! well, if no one is using it and it gets us better perfomance + simplifies the code, it looks great :)
I have pushed Pollen v3.0 (incrementing the major version number because strictly speaking, this is not a backward-compatible change, but in practice, it’s not going to disrupt many proejcts).