summaryrefslogtreecommitdiff
path: root/libraries/bytestring
Commit message (Collapse)AuthorAgeFilesLines
* Bump bytestring submoduleBen Gamari2022-04-291-0/+0
| | | | Update to current `master`.
* Bump bytestring submoduleBen Gamari2022-04-061-0/+0
|
* Bump bytestring submodule to 0.11.2.0Bodigrim2021-12-091-0/+0
| | | | | | | | Both tests import `Data.ByteString`, so the change in allocations is more or less expected. Metric Increase: T19695 T9630
* Bump bytestring submodule to 0.11.1.0Ben Gamari2021-03-101-0/+0
|
* Fix array and cleanup conversion primops (#19026)Sylvain Henry2021-03-031-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The first change makes the array ones use the proper fixed-size types, which also means that just like before, they can be used without explicit conversions with the boxed sized types. (Before, it was Int# / Word# on both sides, now it is fixed sized on both sides). For the second change, don't use "extend" or "narrow" in some of the user-facing primops names for conversions. - Names like `narrowInt32#` are misleading when `Int` is 32-bits. - Names like `extendInt64#` are flat-out wrong when `Int is 32-bits. - `narrow{Int,Word}<N>#` however map a type to itself, and so don't suffer from this problem. They are left as-is. These changes are batched together because Alex happend to use the array ops. We can only use released versions of Alex at this time, sadly, and I don't want to have to have a release thatwon't work for the final GHC 9.2. So by combining these we get all the changes for Alex done at once. Bump hackage state in a few places, and also make that workflow slightly easier for the future. Bump minimum Alex version Bump Cabal, array, bytestring, containers, text, and binary submodules
* Bump bytestring submoduleBen Gamari2021-02-141-0/+0
| | | | Teach it to use unsafeWithForeignPtr where appropriate.
* [Sized Cmm] properly retain sizes.Moritz Angermann2020-11-261-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | This replaces all Word<N> = W<N># Word# and Int<N> = I<N># Int# with Word<N> = W<N># Word<N># and Int<N> = I<N># Int<N>#, thus providing us with properly sized primitives in the codegenerator instead of pretending they are all full machine words. This came up when implementing darwinpcs for arm64. The darwinpcs reqires us to pack function argugments in excess of registers on the stack. While most procedure call standards (pcs) assume arguments are just passed in 8 byte slots; and thus the caller does not know the exact signature to make the call, darwinpcs requires us to adhere to the prototype, and thus have the correct sizes. If we specify CInt in the FFI call, it should correspond to the C int, and not just be Word sized, when it's only half the size. This does change the expected output of T16402 but the new result is no less correct as it eliminates the narrowing (instead of the `and` as was previously done). Bumps the array, bytestring, text, and binary submodules. Co-Authored-By: Ben Gamari <ben@well-typed.com> Metric Increase: T13701 T14697
* Bump submodulesBen Gamari2020-09-231-0/+0
| | | | | | * Bump bytestring to 0.10.12.0 * Bump Cabal to 3.4.0.0-rc3 * Bump Win32 to 2.10.0.0
* Bump bytestring and text submoduleswip/landingSylvain Henry2020-06-171-0/+0
|
* Fix unused-import warningsDavid Eichmann2018-11-221-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch fixes a fairly long-standing bug (dating back to 2015) in RdrName.bestImport, namely commit 9376249b6b78610db055a10d05f6592d6bbbea2f Author: Simon Peyton Jones <simonpj@microsoft.com> Date: Wed Oct 28 17:16:55 2015 +0000 Fix unused-import stuff in a better way In that patch got the sense of the comparison back to front, and thereby failed to implement the unused-import rules described in Note [Choosing the best import declaration] in RdrName This led to Trac #13064 and #15393 Fixing this bug revealed a bunch of unused imports in libraries; the ones in the GHC repo are part of this commit. The two important changes are * Fix the bug in bestImport * Modified the rules by adding (a) in Note [Choosing the best import declaration] in RdrName Reason: the previosu rules made Trac #5211 go bad again. And the new rule (a) makes sense to me. In unravalling this I also ended up doing a few other things * Refactor RnNames.ImportDeclUsage to use a [GlobalRdrElt] for the things that are used, rather than [AvailInfo]. This is simpler and more direct. * Rename greParentName to greParent_maybe, to follow GHC naming conventions * Delete dead code RdrName.greUsedRdrName Bumps a few submodules. Reviewers: hvr, goldfire, bgamari, simonmar, jrtc27 Subscribers: rwbarton, carter Differential Revision: https://phabricator.haskell.org/D5312
* Bump bytestring submoduleBen Gamari2017-02-091-0/+0
|
* Revert accidental submodule updatesThomas Miedema2016-06-181-0/+0
| | | | | Commit 77bb09270c70455bbd547470c4e995707d19f37d seems to have accidentally set some submodules to earlier versions. Undo this.
* Re-add FunTy (big patch)Simon Peyton Jones2016-06-151-0/+0
| | | | | | | | | | | | | | | | | | | | | | With TypeInType Richard combined ForAllTy and FunTy, but that was often awkward, and yielded little benefit becuase in practice the two were always treated separately. This patch re-introduces FunTy. Specfically * New type data TyVarBinder = TvBndr TyVar VisibilityFlag This /always/ has a TyVar it. In many places that's just what what we want, so there are /lots/ of TyBinder -> TyVarBinder changes * TyBinder still exists: data TyBinder = Named TyVarBinder | Anon Type * data Type = ForAllTy TyVarBinder Type | FunTy Type Type | .... There are a LOT of knock-on changes, but they are all routine. The Haddock submodule needs to be updated too
* Update bytestring submodule to 0.10.8.1 release tagHerbert Valerio Riedel2016-05-151-0/+0
|
* Update bytestring submodule to 0.10.8.0 release tagHerbert Valerio Riedel2016-05-041-0/+0
|
* Update bytestring submodule to latest snapshotHerbert Valerio Riedel2016-03-281-0/+0
| | | | | | | | | Most notably, this pulls in the following changes > Fix breakByte and spanByte rewrite rules > Implement `stripPrefix`/`stripSuffix` The first patch is related to #11688
* Update bytestring submoduleHerbert Valerio Riedel2015-12-021-0/+0
| | | | Differential Revision: https://phabricator.haskell.org/D1549
* Update bytestring submodule to 0.10.6.0 release tagHerbert Valerio Riedel2015-03-201-0/+0
|
* Update bytestring submoduleHerbert Valerio Riedel2015-01-191-0/+0
| | | | | | | This pulls in - https://github.com/haskell/bytestring/pull/40 (which is related to #9992) - https://github.com/haskell/bytestring/pull/38
* Update `bytestring` submoduleHerbert Valerio Riedel2014-12-181-0/+0
| | | | this just pulls in the version bump to 0.10.6
* Update `bytestring` submodule to 0.10.6.0 RCHerbert Valerio Riedel2014-12-141-0/+0
| | | | | NB: this still carries the wrong version number 0.10.5.0 but will be released as 0.10.6.0
* Update to (unreleased) `deepseq-1.4.0.0`Herbert Valerio Riedel2014-11-151-0/+0
| | | | | | | | | | | | | | | | | | | This pulls in the new `Generic`-based `-XDefaultSignature`-based default implementation for `rnf`[1], and will be interesting to use in combination with the soon to be merged `-XDeriveAnyClass` extension. This requires updating several other submodules as well in order to relax the upper bound on `deepseq` and/or in a few cases to avoid relying on the default method implementation of `rnf`: - `Cabal` - `bytestring` - `containers` - `parallel` - `process` - `time` [1]: http://permalink.gmane.org/gmane.comp.lang.haskell.libraries/23031
* Update `bytestring` to final 0.10.4.0 releaseHerbert Valerio Riedel2013-10-101-0/+0
|
* Update `bytestring` library to latest upstream HEADHerbert Valerio Riedel2013-10-041-0/+0
|
* Revert "Update submodules"Jan Stolarek2013-08-291-0/+0
| | | | This reverts commit 6df74382986fad6d9132e03e1f19303be8f19672.
* Update submodulesJan Stolarek2013-08-291-0/+0
| | | | I didn't notice that rebase did not update submodules. Fixing now.
* Update `bytestring` library to latest HEADHerbert Valerio Riedel2013-08-291-0/+0
| | | | | This also folds the new upstream repo at Github into GHC's `bytestring` Git repo, so that we can directly track upstream from there in the future.
* Update submodule versionsIan Lynagh2013-02-161-0/+0
|
* Update bytestring and terminfo reposIan Lynagh2013-01-111-0/+0
| | | | | bytestring fixes #7556. terminfo fixes #7281.
* Use submodules for repositories with upstreamsIan Lynagh2012-11-251-0/+0
View Lorry Controller Status