futhark-server 1.4.1.1 → 1.5.0.0

raw patch · 3 files changed

+13/−10 lines, 3 filesPVP ok

version bump matches the API change (PVP)

API changes (from Hackage documentation)

Files

• CHANGELOG.md +4/−0
• futhark-server.cabal +1/−1
• src/Futhark/Server.hs +8/−9

@@ -1,5 +1,9 @@ # Revision history for futhark-server +## 1.5.0.0 -- 2026-09-08++* `outputUnique` is now `outputFresh`.+ ## 1.4.1.1 -- 2026-08-20  * Fixed bug in `cmdShape` which would read only first line from the server.

@@ -1,6 +1,6 @@ cabal-version:      2.4 name:               futhark-server-version:            1.4.1.1+version:            1.5.0.0 synopsis: Client implementation of the Futhark server protocol.  description: Provides an easy way to interact with a running Futhark

@@ -373,22 +373,21 @@   }   deriving (Eq, Ord, Show) --- | The type of an input of an entry point.  If 'inputConsumed', then--- the value passed in a 'cmdCall' must not be used again (nor any of--- its aliases).+-- | The type of an input of an entry point. If 'inputConsumed', then the value+-- passed in a 'cmdCall' must not be used again (nor any of its aliases). data InputType = InputType   { inputConsumed :: Bool,     inputType :: TypeName   }   deriving (Eq, Ord, Show) --- | The type of an output of an entry point.  If 'outputUnique', then--- the value returned does not alias any of the inputs.  See the--- Futhark language manual itself for more details - the implications--- are quite subtle (but you can ignore them unless you manually use--- type annotations to make some entry point parameters unique).+-- | The type of an output of an entry point. If 'outputFresh', then the value+-- returned does not alias any of the inputs. See the Futhark language manual+-- itself for more details - the implications are quite subtle (but you can+-- ignore them unless you manually use type annotations to make some entry point+-- parameters unique). data OutputType = OutputType-  { outputUnique :: Bool,+  { outputFresh :: Bool,     outputType :: TypeName   }   deriving (Eq, Ord, Show)