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

Enable LSP development #1011

Merged
merged 4 commits into from
Sep 15, 2023
Merged

Enable LSP development #1011

merged 4 commits into from
Sep 15, 2023

Conversation

koliyo
Copy link
Contributor

@koliyo koliyo commented Sep 15, 2023

  • Compile hylo compiler as a library
  • Public constructors for SourcePosition

Package.swift Outdated
@@ -16,6 +16,7 @@ let package = Package(
products: [
.executable(name: "hc", targets: ["hc"]),
.executable(name: "hylo-demangle", targets: ["hylo-demangle"]),
.library(name: "hc-lib", targets: ["Driver"])
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
.library(name: "hc-lib", targets: ["Driver"])
.library(name: "Hylo", targets: ["Driver"])

Hylo seems to better fit how Swift libraries are typically named. I am on the fence as to whether it should rather be HyloCompiler, but I can easily imagine the library's API will eventually let us interact with the interpreter we'll have to ship for compile-time evaluation.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I am open to whatever name you guys prefer. I am very new to Swift in general and don't have a lot of experience with Swift ecosystem and best practices.

Copy link
Contributor

Choose a reason for hiding this comment

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

Let's go with Hylo to start. We can split into smaller specialized libraries in the future if the need emerges.

@kyouko-taiga kyouko-taiga merged commit 6652164 into hylo-lang:main Sep 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants