Compilation error when using resource_group with (scope = moudle)

[Haupc]

Discord user ID

haupc

Describe your question in detail.

I'm trying to use resource group to store object but getting compilation failed: Compilation error

When define the resource group:

    #[resource_group(scope = module)]
    struct ResourceGroup {}

and then compile, I got an error:

error[E01002]: unexpected token
   ┌─ multi_strategy_vault.move:62:30
   │
62 │     #[resource_group(scope = module)]
   │                              ^^^^^^
   │                              │
   │                              Unexpected 'module'
   │                              Expected attribute name value

I'm doing it follow this aip: https://github.com/aptos-foundation/AIPs/blob/main/aips/aip-9.md#within-the-framework

What error, if any, are you getting?

compilation failed: Compilation error

error[E01002]: unexpected token
   ┌─ multi_strategy_vault.move:62:30
   │
62 │     #[resource_group(scope = module)]
   │                              ^^^^^^
   │                              │
   │                              Unexpected 'module'
   │                              Expected attribute name value

What have you tried or looked at? Or how can we reproduce the error?

complie

Which operating system are you using?

macOS

Which SDK or tool are you using? (if any)

Aptos CLI

Describe your environment or tooling in detail

No response

[0x-j]

can you try writing #[resource_group_member(group = aptos_framework::object::ObjectGroup)]?

[Haupc]

I'm trying to create another resource group to use. not using existing resource group. I can use scope = global but can NOT use scope = module in the code above.

The aip-9 (https://github.com/aptos-foundation/AIPs/blob/main/aips/aip-9.md#within-the-framework) mentioned that

Within the Gas Schedule and the VM

The implications for the gas schedule are:

    Reading a single resource from a resource group results in a charge for all the data within a resource group.
    Writing a single resource to a resource group results in a charge for all the data within a resource group.

So, I think that using shared global scope resource group aptos_framework::object::ObjectGroup is not best for gas saving.
The aip also said that:

The attribute resource_group has the parameter scope that limits the location of other entries within the resource group:

    `module` — only resources defined within the same module may be stored within the same resource group.
    `address` — only resources defined within the same address may be stored within the same resource group.
    `global` — there are no limitations to where the resource is defined, any resource can be stored within the same resource group.

I Think that module is the best pratice for this case.

[0x-j]

i see, how about using it like this https://github.com/aptos-labs/aptos-names-contracts/blob/001d9998d33bb31e693dc7005fc513deabadf748/core_v2/sources/v2_1_domains.move#L91

[Haupc]

as you can see in the file line 83: #[resource_group(scope = global)].
scope = global works fine for me.
Actually I'm using scope = address and I think that it's doing great.
I'm just wonder if scope = module work?

[0x-j]

i think the link i had above is at module level? group = addr::module::ObjectGroup