Swift 6 Support and Base URL Handling Update

[1amageek]

This PR introduces updates to support Swift 6, including adjustments to concurrency-related features and the Sendable conformance across relevant types.

Swift 6 Compatibility:

Updated swift-tools-version to 6.0 in Package.swift.

Added Sendable conformance to various structs, enums, and classes in compliance with Swift 6’s stricter concurrency rules.

Refined baseURL Handling:

Modified OKRouter to require an explicit baseURL argument in the asURLRequest() method rather than relying on a static baseURL.
Refactored OllamaKit to store baseURL as an instance property, allowing more flexible and testable configurations.
Updated all API request functions to pass baseURL explicitly when creating URLRequest objects.

These updates help ensure compatibility with Swift 6 while making the base URL configuration more flexible and consistent.

[kevinhermawan]

Great work, @1amageek! Could you kindly explain its significance? Why do we need to make all types conform to Sendable? IMHO, the current code is working well in Swift 6.0. I’m eager to learn more about this concept. 😃

Additionally, could you please run the Playground application and verify that everything functions smoothly without any modifications required. Thanks!

[1amageek]

Thank you for your insightful question and feedback!

Sendable in Swift 6:

• Prevents data races
• Enables thread-safety checks
• Clear design intent
• Future-proofs code

Current code works due to implicit conformance or non-concurrent usage

Explicit Sendable benefits:

• Compile-time safety checks
• Clear thread-safety documentation
• Enables use in other concurrent contexts

I have already implemented it in my project, and it is working without any issues.

[kevinhermawan]

Hi @1amageek, could you please verify and fix the issues by running the Playground app?

[kevinhermawan]

Hey @1amageek, I’m happy for all your contributions! But I’m a bit bummed that changing the data type from Double to Float will break the implementation. This library is used in a lot of apps, so we should probably stick with Double.

Could we stick this PR (or create a new one) just for making OllamaKit conform to Sendable to avoid any unexpected issues?

[1amageek]

@kevinhermawan

Thank you always for your amazing work.
I am developing a Swift Agent using your repository.
It allows you to define Agents declaratively, similar to SwiftUI.
Please feel free to try it out if you're interested.

I am also using OllamaKit there.

https://github.com/1amageek/SwiftAgent

[kevinhermawan]

It looks like you have integrated swift-json-schema into this PR? That's awesome! I'll go check it out in my spare time!

[kevinhermawan]

@kevinhermawan

Thank you always for your amazing work. I am developing a Swift Agent using your repository. It allows you to define Agents declaratively, similar to SwiftUI. Please feel free to try it out if you're interested.

I am also using OllamaKit there.

https://github.com/1amageek/SwiftAgent

This is super cool! I’ll definitely check it out in my free time.