RFR: 8371667: Shenandoah: Re-design alloc request type enum for better efficiency and cleaner code [v13]

[Xiaolong Peng]

On Mon, 17 Nov 2025 17:43:56 GMT, Kelvin Nilsen <kdnilsen at openjdk.org> wrote:

>> Yes, I am not sure why we have the case for `_alloc_shared_gc` here. But I would leave it for extra safety in this "optimization/cleanup" change. We can yank this case later.
>
> Humongous objects do move under full gc, and may eventually move under concurrent GC with some refactoring.

I have added the line  `case ShenandoahAllocRequest::_alloc_shared_gc:` back.
For full gc, we may move humongous objects in compaction, not by evacuation, so it won't call into `ShenandoahFreeSet::allocate` method, right?

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/28247#discussion_r2535086190