Repository navigation
Pragma - #141
Merged
Merged
Pragma#141
Conversation
Y-Nak
force-pushed
the
pragma
branch
2 times, most recently
from
October 29, 2026 13:16
0f2d395 to
060f22b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Solcore and Solidity share the
.solextension, so the language server and editor integrations also picked up Solidity files. Every Solcore source file must now begin withpragma solcore;, and the tools use it to recognize Solcore files.pragma solcore;without arguments (comments may precede it)..solfiles with the pragma, and auto-imports go after it..solfiles to Solidity support.