Skip to content

Add id for #multiple-platforms FAQ link #40

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.

Sign up for GitHub

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

Merged
rtfeldman merged 1 commit into from
Nov 30, 2025
+1 −1
Merged

Add id for #multiple-platforms FAQ link #40

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion website/content/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -387,7 +387,7 @@ Dependent types are too risky of a bet for Roc to take. They have been implement

Perhaps more success stories will emerge over time, but in the meantime it remains an open question whether dependent types are net beneficial in practice to application development. Further experimentation would be required to answer this question, and Roc is not the right language to do those experiments.

## [Can one application have multiple platforms? Can platforms compose?](#multiple-platforms)
## [Can one application have multiple platforms? Can platforms compose?](#multiple-platforms) {#multiple-platforms}

The short answer to each of these questions is "No." To understand why, it's helpful to look at this from the platform author's perspective.

Expand Down
Loading