I have two main issues with this.

1. The current implementation wastes memory for those who do not care about this feature (i.e. most people)
2. The current implementation feels dodgy. It's using regex for no good reason and expensively so, it seems like it's a 1:1 port of JS code without porting it to the target language's strength.

Other than that I'm not sure on the overall merit of the PR. Is this a commonly requested feature? If you do a simple search of nameAcronym on GitHub you don't get that many results of people actually using it.

I have two main issues with this.

1. The current implementation wastes memory for those who do not care about this feature (i.e. most people)
2. The current implementation feels dodgy. It's using regex for no good reason and expensively so, it seems like it's a 1:1 port of JS code without porting it to the target language's strength.

Other than that I'm not sure on the overall merit of the PR. Is this a commonly requested feature? If you do a simple search of nameAcronym on GitHub you don't get that many results of people actually using it.

1 & 2. Fair points. Unfortunately, I don't know how to fix that, as I am very new to regex usage. Reviews are welcome.

This is not a requested feature, but I thought it would fit in between the other features, as others pointed out, like Message.system_content, Member.top_role, etc.

From what I understood, I believe ''.join(word[0] for word in self.name.split()) suffices as a way without regex?

From what I understood, I believe ''.join(word[0] for word in self.name.split()) suffices as a way without regex?

Unfortunately not, there are edge cases that apply to this, such as "X of Y" and "X's thing".
It's a bit more involved.

Unfortunately not, there are edge cases that apply to this, such as "X of Y" and "X's thing".
It's a bit more involved.

Interesting, I just tested the examples you gave on both my mobile and desktop client, and they show up as "XoY" and "Xt", respectively. I ran my code snippet and it did get it right.