Thank you for your replies and provided links.
Unfortunately, I cannot provide the code as my boss thinks it
could provide some extra information - definitely not Haskellish,
but other.
Nevetheless, your contribution was helpful and I was able to tune
the code to get even better perofmance.
Hello!
I've used Haskell and GHC to solve particular real life application. 4
tools were developed and their function is almost the same - they
modify textual input according to patterns found in the text. Thus, it
Hmm, modification can be a problem for ByteStrings, since it
Hi John,
I've used Haskell and GHC to solve particular real life application. 4
tools were developed and their function is almost the same - they
modify textual input according to patterns found in the text. Thus, it
Hmm, modification can be a problem for ByteStrings, since it entails
Hi,
- If bytestring is not suitable for text manipulation, is there
something faster than lists?
Have a look at the text package[1].
However the performance issues seem odd: text is based on bytestring.
2011/12/5 Simon Hengel s...@typeful.net
Hi,
- If bytestring is not suitable for text manipulation, is there
something faster than lists?
Have a look at the text package[1].
Cheers,
Simon
[1]
On Mon, Dec 5, 2011 at 6:09 AM, Yves Parès limestr...@gmail.com wrote:
However the performance issues seem odd: text is based on bytestring.
This is not the case. Text is based on ByteArray#, GHC internal type for
blocks of bytes. The text package depends on the bytestring package because
it
On Monday 05 December 2011, 14:14:56, John Sneer wrote:
I've used Haskell and GHC to solve particular real life application. 4
tools were developed and their function is almost the same - they
modify textual input according to patterns found in the text. Thus, it
Hmm, modification can be a
Oh, sorry, my bad.
I misunderstood the dependency.
2011/12/5 Johan Tibell johan.tib...@gmail.com
On Mon, Dec 5, 2011 at 6:09 AM, Yves Parès limestr...@gmail.com wrote:
However the performance issues seem odd: text is based on bytestring.
This is not the case. Text is based on ByteArray#,
I wonder what profiling tells you, you should identify where your
performance problems actually are before trying to optimise.
Some things that might help are using something like Blaze-Builder[1] to
construct your bytestrings for output. I'm hoping that they're sufficiently
lazy that you can
