You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The suggestion to move system prompts to .mts files is an interesting approach, particularly in the context of leveraging modern JavaScript features like runtime compilation and the top-level await syntax. This would allow for a more efficient execution model compared to using eval, which can be computationally expensive and potentially dangerous if not handled properly.
However, it's crucial to evaluate the broader implications of this change:
Compatibility: Ensure that any users or environments that depend on current system prompts are compatible with .mts files.
Testing: Thoroughly test the new implementation to ensure all functionality remains intact and no regressions occur.
Documentation: Update documentation to reflect the new file format and any changes in how system prompts should be managed.
In summary, while moving system prompts to .mts files could offer performance benefits, it must be done with careful consideration of compatibility, testing, and documentation updates to avoid potential issues for existing users.
To leverage runtime, move out of eval.
The text was updated successfully, but these errors were encountered: