Hi!
Thanks for reviewing issues #9 and #10. As a non-native speaker, I did use LLMs to craft these issues, but they have been manually reviewed before reporting. I understand these issues may be controversial. That's why I would like to discuss them with you.
For the issue, could the documentation explicitly state that StackVec::insert intentionally requires index < len and does not support tail insertion at index == len, so users should call push for that case? I understand this is rather subtle. However, it would be better if there were no potential for misinterpretation. For context, Vec::insert allows 'index == len'. Thank you for your time!
Hi!
Thanks for reviewing issues #9 and #10. As a non-native speaker, I did use LLMs to craft these issues, but they have been manually reviewed before reporting. I understand these issues may be controversial. That's why I would like to discuss them with you.
For the issue, could the documentation explicitly state that
StackVec::insertintentionally requiresindex < lenand does not support tail insertion atindex == len, so users should call push for that case? I understand this is rather subtle. However, it would be better if there were no potential for misinterpretation. For context, Vec::insert allows 'index == len'. Thank you for your time!