Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expand "Overview of Languages Compiling to UPLC" #6558

Merged
merged 1 commit into from
Oct 11, 2024
Merged

Expand "Overview of Languages Compiling to UPLC" #6558

merged 1 commit into from
Oct 11, 2024

Conversation

zliu41
Copy link
Member

@zliu41 zliu41 commented Oct 10, 2024

Adding some more content and arguments.

@zliu41 zliu41 added the No Changelog Required Add this to skip the Changelog Check label Oct 10, 2024
@zliu41 zliu41 requested a review from a team October 10, 2024 15:59
@@ -50,6 +59,9 @@ Another disadvantage of eDSLs is that it is harder, compared to the other two ap
This stems from the nature of eDSLs, which are libraries that construct and manipulate ASTs.
Since they do not have direct access to the host language's ASTs, it can be challenging to retrieve information related to the source code, such as variable names, module names and code locations.

Lastly, eDSLs often cannot leverage the host language's existing library ecosystem.
Again, using an eDSL involves constructing and manipulating ASTs rather than writing regular programs, which means many existing libraries would be inapplicable.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But it's very similar to what we have in Plinth? We have to reimplement everything to make sure it's Plinth-compatible and not just Haskell.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes but this is more particular to Plinth/Haskell than a general limitation of that type of language. As I said in the footnote, "This statement is not entirely true for Plutus Tx, a subset of Haskell. Due to certain GHC-specific technical limitations, it can't easily reuse many functions and operations from the base library, so it ships with its own standard library instead."

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, fair enough, I just do what I do best: unproductive nitpicking. Sorry!

@zliu41 zliu41 merged commit 029467a into master Oct 11, 2024
9 checks passed
@zliu41 zliu41 deleted the zliu41/cmp branch October 11, 2024 13:32
v0d1ch pushed a commit to v0d1ch/plutus that referenced this pull request Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
No Changelog Required Add this to skip the Changelog Check
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants