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

Swift and other programming languages #19

Open
mobile-appz opened this issue Jun 8, 2024 · 2 comments
Open

Swift and other programming languages #19

mobile-appz opened this issue Jun 8, 2024 · 2 comments
Labels
feature New feature or request

Comments

@mobile-appz
Copy link

mobile-appz commented Jun 8, 2024

Is it possible to interpret Swift code with this somehow? That would be very useful for mobile app development.

@mlejva
Copy link
Member

mlejva commented Jun 8, 2024

Hey @mobile-appz not right now but we're working on adding more languages but we haven't been planning on adding Swift.

Looking at general Swift support in Jupyter, it looks like it's possible.

But would just general Swift be useful for you without having access to macOS? Our sandboxes are based on Linux you wouldn't be able to used iOS libraries that you need for mobile development

@mobile-appz
Copy link
Author

mobile-appz commented Jun 8, 2024

Hey @mobile-appz not right now but we're working on adding more languages but we haven't been planning on adding Swift.

Looking at general Swift support in Jupyter, it looks like it's possible.

But would just general Swift be useful for you without having access to macOS? Our sandboxes are based on Linux you wouldn't be able to used iOS libraries that you need for mobile development

Thanks for info. That's good to know it works with Jupyter. Would probably need at least the foundation library for it to be worthwhile, and ideally, SwiftUI library would be good. Presumably there is a way of getting this all ported to macOS though even if it's Linux based. Then app code could be generated in LLM, tested, iterated and improved all before its even output as a solution. It would really increase productivity. The current workflow is: define problem, use Llm to generate code to solve problem, enter code in Xcode, compile code in Xcode, send errors back to Llm and repeat. This could be made much more efficient with a code interpreter before the code reaches Xcode.

@ValentaTomas ValentaTomas added the feature New feature or request label Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants