mirror of
https://github.com/rojo-rbx/rojo.git
synced 2026-10-23 14:01:37 +00:00
b47eef1173
- Introduced a new endpoint `/api/syncback` for one-click full sync from Roblox Studio to the filesystem, eliminating the need for an active WebSocket connection. - Implemented `SyncbackRequest` and `ServiceChunk` structures to handle service-level properties and child instances during syncback. - Enhanced `encodeService` to include ObjectValue carriers for accurate reference handling and prevent data loss. - Updated the syncback process to utilize Luau-style relative paths for reference attributes, improving path management and consistency. - Integrated session caching in the matching algorithm to optimize performance during syncback operations. These changes significantly improve the live syncback experience, ensuring reliable data synchronization and enhanced performance during development.
51 lines
2.5 KiB
Markdown
51 lines
2.5 KiB
Markdown
# Native Attribute for Functions
|
|
|
|
**Status**: Implemented
|
|
|
|
## Summary
|
|
|
|
This RFC proposes a function-level `@native` attribute to request native compilation for individual functions, independent of the script-level `--!native` comment directive.
|
|
|
|
## Motivation
|
|
|
|
Luau's native compiler currently compiles whole scripts annotated with `--!native` comment directive. The compiler imposes an upper limit on the memory consumed by the generated native code which makes it important to target native compilation for functions that will benefit from it the most. This might force creators to break their code organization and move unrelated functions together to scripts marked `--!native`. In this RFC, we propose a function-level `@native` attribute to facilitate developers to request native compilation for individual functions. In the future, we want Luau's native compiler to automatically pick functions for native compilation, making the `--!native` comment directive redundant. Since compiler heuristics can be suboptimal, the proposed `@native` attribute would still remain useful by providing creators with a way to force native compilation of functions that were not automatically chosen by the compiler but would benefit significantly from native execution.
|
|
|
|
## Design
|
|
|
|
Syntactically, the `@native` attribute takes no parameters. It can be used on both top-level and inner functions. It does not apply recursively to the functions defined within the lexical scope of the attributed function. These "inner" functions have to be explicitly attributed for native compilation.
|
|
|
|
In the following example, only `parent` will be natively compiled.
|
|
|
|
```lua
|
|
@native
|
|
function parent()
|
|
function child()
|
|
-- do something
|
|
end
|
|
-- do something
|
|
end
|
|
```
|
|
|
|
On the other hand, in this example, both `parent` and `child` will be natively compiled.
|
|
|
|
```lua
|
|
@native
|
|
function parent()
|
|
@native
|
|
function child()
|
|
-- do something
|
|
end
|
|
-- do something
|
|
end
|
|
```
|
|
|
|
## Drawbacks
|
|
|
|
Introducing this attribute will have two adverse consequences:
|
|
|
|
1. It will increase the complexity of the implementation which will now have to make compilation decisions on a per-function basis.
|
|
2. Experience code will be strewn with occurrences of `@native` attribute.
|
|
|
|
## Alternatives
|
|
|
|
The alternative would be to not provide this attribute and rely on `--!native` comment directive to make compilation decisions on a per-script basis. This might force developers to break their code organization and move unrelated functions together but it does not prevent them from getting performance benefits.
|