Closed yuxuan-xie closed 1 month ago
Thanks for the review. I fully understand your concern. Adapting some transparent strategy that does not support explicit renaming is much more advantageous in terms of maintenance and consistency across the whole codebase. But it seems that the usecase in #505, which is also my usecase, is a bit too much a corner case so developers are not willing to pay too many efforts to this. So for now, I will just use this roughly patched fork in my own project and close this pull request. If someone is willing to fix this problem with a more compatible solution, I am very glad to help.
A workaround for #505.