Deprecating things for better performance #425
Replies: 3 comments 11 replies
-
Interesting. I suppose that would solve the issue with needing to clear the attributes caches when The downside I think is many users might not notice this is needed, and it's not easy to test such behavior, as you can only freeze Alba once. An alternative could be to have something like Yet another possibility is to continue doing something similar to |
Beta Was this translation helpful? Give feedback.
-
|
Other methods that aren't ideal with the approach I took in #424
Both are ways to not include one of the attributes in the result, which can also be done via returning But to be clear, I don't want to encourage you to deprecate anything. I'm just exploring how Alba could be made faster, it doesn't have to be merged if you'd rather keep this flexibility in the gem. |
Beta Was this translation helpful? Give feedback.
-
|
@trevorturk Hi Trevor, sorry that I forgot to mention you in this discussion. If you have some ideas, please make a post here! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
From #424
I'd like to discuss performance and deprecation further here.
My personal idea is to add
Alba.freezeso that we can make sure every config is static. Typically it would be called in the initializer.@byroot What do you think? Do you have any method you want to deprecate?
Beta Was this translation helpful? Give feedback.
All reactions