On 14/10/2011, at 12:37, Bas van Dijk wrote:
If there's need for a specific Show instance for Vectors of Word8s we
can always add one directly to vector. (Roman, what are your thoughts
on this?)
Personally, I think that ByteString and especially Vector Word8 aren't strings
and shouldn't be
On 15/10/2011, at 12:26, Roman Leshchinskiy wrote:
On 14/10/2011, at 12:37, Bas van Dijk wrote:
If there's need for a specific Show instance for Vectors of Word8s we
can always add one directly to vector. (Roman, what are your thoughts
on this?)
Personally, I think that ByteString and
On 15 October 2011 13:34, Roman Leshchinskiy r...@cse.unsw.edu.au wrote:
On 15/10/2011, at 12:26, Roman Leshchinskiy wrote:
On 14/10/2011, at 12:37, Bas van Dijk wrote:
If there's need for a specific Show instance for Vectors of Word8s we
can always add one directly to vector. (Roman, what
Hi,
Am Samstag, den 15.10.2011, 16:15 +0200 schrieb Bas van Dijk:
So what do other people think about this?
having a human-readable Show instance for ByteStrings is definitely a
great plus when debugging code.
Greetings,
Joachim
--
Joachim nomeata Breitner
m...@joachim-breitner.de |
A user recently suggested changing the associativity of ($=) from [[
infixr 0 ]] to [[ infixl 1 ]]. This allows the following expressions
to be equivalent:
run $ enumerator $$ enumeratee =$ enumeratee =$ iteratee
run $ enumerator $= enumeratee $$ enumeratee =$ iteratee
run $ enumerator
On 16 October 2011 01:15, Bas van Dijk v.dijk@gmail.com wrote:
I agree that you shouldn't use ByteStrings or Vectors of Word8s for
Unicode strings. However I can imagine that for quick sessions in ghci
it can be quite handy if they are shown as strings. For example,
currently we have:
On Sat, Oct 15, 2011 at 4:59 PM, John Millikin jmilli...@gmail.com wrote:
A user recently suggested changing the associativity of ($=) from [[
infixr 0 ]] to [[ infixl 1 ]]. This allows the following expressions
to be equivalent:
run $ enumerator $$ enumeratee =$ enumeratee =$ iteratee
This would be a big boon to newbies. When I first started using the
library I would get big errors using $= that were because I didn't
have parenthesis I needed, but didn't realize I needed, despite the
fact that the types seemed to line up.
On Sat, Oct 15, 2011 at 12:40 PM, Michael Snoyman
As a recent newbie, I would like to confirm the parent's report. I
eventually managed to think of the parentheses, but it did leave me
stumped for a while on thursday.
On Sa, 2011-10-15 at 12:49 -0400, David McBride wrote:
This would be a big boon to newbies. When I first started using the
Joachim Breitner m...@joachim-breitner.de wrote:
So what do other people think about this?
having a human-readable Show instance for ByteStrings is definitely a
great plus when debugging code.
I agree and would even go as far as saying that it's generally useful,
even if the data is not
One more thing... The function:
return :: a - Beh a
return x t = x
fails to be causal when a is itself a behaviour, since it specializes to
(after a bit of eta-conversion):
return :: Beh a - Beh (Beh a)
return b t u = b u
which isn't causal. This rules out return, which in turn
On 15 October 2011 20:50, Ertugrul Soeylemez e...@ertes.de wrote:
Roman Leshchinskiy r...@cse.unsw.edu.au wrote:
Personally, I think that ByteString and especially Vector Word8
aren't strings and shouldn't be treated as such. But I wouldn't be
strongly against showing them as strings.
Bas van Dijk v.dijk@gmail.com wrote:
My suggestion was to remove the generic Show instance and add only
specialized instances. This is more work, but will also yield
better results. In particular, it allows specialized string
representations for other types, too.
What exactly is
On 15 October 2011 23:17, Ertugrul Soeylemez e...@ertes.de wrote:
Both instances are valid here, and there is no mechanism to choose one of
them.
There is: OverlappingInstances[1] chooses the most specific instance.
So in case someVector :: Vector Word8 the instance Show (Vector Word8)
is
Hi all,
In this excerpt from the
Automatonhttp://hackage.haskell.org/packages/archive/arrows/0.4.1.2/doc/html/Control-Arrow-Transformer-Automaton.html#t:Automatonpage:
runAutomaton ::
(ArrowLoopChttp://hackage.haskell.org/packages/archive/base/4.2.0.2/doc/html/Control-Arrow.html#t:ArrowLoopa,
hello Aur:
:) You get the point, the author of that package said that he has no enough
time to check for the problem. then I have to solve it myself.
For these kind of packages, maybe the best way to use it is re-write it
myself...
I have see a lot of packages that comes from master thesis or
Hello everyone
I started writing this application but there is some thing missing. I
read this file http://www.viste.com/Linux/Server/WireShark/libpcapformat.pdf
and it say that first 24 bytes are global headers , after that every
packet contains pcap local header . What i am trying to do is ,
17 matches
Mail list logo
