You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,7 @@ It is possible to generate Swift bindings to Java libraries using SwiftJava by u
58
58
59
59
Required language/runtime versions:
60
60
-**JDK 17+**, any recent JDK installation should be sufficient, as only general reflection and JNI APIs are used by this integratio
61
-
-**Swift 6.0.x**, because the library uses modern Swift macros
61
+
-**Swift 6.2.x**, because the library uses modern Swift macros
62
62
63
63
**swift-java jextract**
64
64
@@ -73,7 +73,7 @@ This does require the use of the relatively recent [JEP-454: Foreign Function &
73
73
This is the primary way we envision calling Swift code from server-side Java libraries and applications.
74
74
75
75
Required language/runtime versions:
76
-
-**Swift 6.1**, because of dependence on rich swift interface files
76
+
-**Swift 6.2**, because of dependence on rich swift interface files
77
77
-**JDK 25+**
78
78
- We are validating the implementation using the currently supported non-LTE release, which at present means JDK-25.
79
79
@@ -85,7 +85,7 @@ This mode is more limited in some performance and flexibility that it can offer,
85
85
We recommend this mode when FFM is not available, or wide ranging deployment compatibility is your priority. When performance is paramaunt, we recommend the FFM mode instead.
86
86
87
87
Required language/runtime versions:
88
-
-**Swift 6.1**, because of dependence on rich swift interface files
88
+
-**Swift 6.2**, because of dependence on rich swift interface files
0 commit comments