think basic Haskell syntax for the most part
strikes a pretty good balance on a number of counts), but we can
certainly avoid making it even more complicated and exotic.
Which the present proposal would, in my opinion.
Best,
/Henrik
--
Henrik Nilsson
School of Computer Science
The University of N
, the inherent asymmetry of the proposal (the
last argument position is special as, for certain kinds of
expressions, parentheses may be omitted there but not elsewhere)
is also deeply unsettling.
Best,
/Henrik
--
Henrik Nilsson
School of Computer Science
The University of Nottingham
n...@cs.not
convenience of essentially
one-to-one mappings between module and file names, I think this
proposal would be a step in the right direction, if feasible.
Best,
/Henrik
--
Henrik Nilsson
School of Computer Science
The University of Nottingham
n...@cs.nott.ac.uk
This message and any attachment
integrated
into the HP.
So, for (general) teaching, at least, stability over new features any
day.
Best,
/Henrik
--
Henrik Nilsson
School of Computer Science
The University of Nottingham
n...@cs.nott.ac.uk
This message and any attachment are intended solely for the addressee and may
contain
--
Henrik Nilsson
School of Computer Science
The University of Nottingham
n...@cs.nott.ac.uk
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
to overloading of literals
for a specific case.
Best,
/Henrik
--
Henrik Nilsson
School of Computer Science
The University of Nottingham
n...@cs.nott.ac.uk
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org
something? E.g. is the idea that sharing of fields
only applies to fields of monomorphic type, i.e. whose type can be
declared globally?
Best,
/Henrik
--
Henrik Nilsson
School of Computer Science
The University of Nottingham
n...@cs.nott.ac.uk
are not.
No, I agree completely with Malcolm: not taking the time to
quote ONLY what is of relevance to provide the immediately
relevant context for a point one wishes to make is a failure
of communication and, indeed, an abuse of other's time.
Thanks, Malcolm, well said!
/Henrik
--
Henrik Nilsson
School
are a rather surprising use of list literals.
Maybe. But not more surprising than how, say, numeric literals
are used in many EDSLs.
I also like George's proposal.
Best,
/Henrik
--
Henrik Nilsson
School of Computer Science
The University of Nottingham
n...@cs.nott.ac.uk
, because the operators may
come from various external libraries that one really would like to use.
The list comprehension interference is strictly confined to modules
where quasiquoting is enabled.
Best,
/Henrik
--
Henrik Nilsson
School of Computer Science
The University of Nottingham
n...@cs.nott.ac.uk
!
/Henrik
--
Henrik Nilsson
School of Computer Science
The University of Nottingham
n...@cs.nott.ac.uk
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
at all.
Best,
/Henrik
--
Henrik Nilsson
School of Computer Science
The University of Nottingham
n...@cs.nott.ac.uk
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
is useful.
I plan to tackle it in the next couple of months.
Would this also address how plain old Algebraic Data Types and type
classes work together? The issues seems related.
Best,
/Henrik
--
Henrik Nilsson
School of Computer Science and Information Technology
The University of Nottingham
.
Best regards,
/Henrik
--
Henrik Nilsson
School of Computer Science and Information Technology
The University of Nottingham
[EMAIL PROTECTED]
This message has been checked for viruses but the contents of an attachment
may still contain software viruses, which could damage your computer system
a syntactic shorthand for signatures with the
foralls mentioned explicitly.
Best regards,
/Henrik
--
Henrik Nilsson
School of Computer Science and Information Technology
The University of Nottingham
[EMAIL PROTECTED]
This message has been scanned but we cannot guarantee that it and any
attachments
libraries really rely on this, it would be
nice to know that this is universally supported by all ar programs, linkers,
compilers, etc.
Alternatively, maybe one should reconsider how object files are named.
/Henrik
--
Henrik Nilsson
Yale University
Department of Computer Science
[EMAIL PROTECTED
16 matches
Mail list logo