Displaying 12 results from an estimated 12 matches for "utilitarian".
2017 Jun 19
3
the root cause is CP, was: A tagged architecture, the elephant in the undef / poison room
...nction-inlining issue:
[1. this function *always* executes statement S,
F(a) {
If (a == a) S;
}
but in llvm if you inline it and “a” happens to be “undef” then nothing can
be said about whether statement S is executed. This is indefensible.]
My belief is this: that llvm exists for a utilitarian purpose,
and that llvm currently violates that utilitarian goal by violating
the users expectations in the function-inlining example.
So the question is, where do you stand ?
Peter Lawrence.
> On Jun 19, 2017, at 9:35 AM, Sanjoy Das <sanjoy at playingwithpointers.com> wrote:
>
&...
2018 May 08
5
download.file does not process gz files correctly (truncates them?)
...e would
> create problems for users and programmers who do. The current heuristic/hack
> is in line with the compatibility approach: it detects files that are
> obviously binary, so it changes the default behavior only for cases when it
> would obviously cause damage.
>From a purely utilitarian standpoint, there are far more users who do
not carefully read the documentation than users who do ;)
(I'd also argue that basing the decision on the file extension is
suboptimal, and it would be better to use the mime type if provided by
the server)
Hadley
--
http://hadley.nz
2017 Jun 19
4
the root cause is CP, was: A tagged architecture, the elephant in the undef / poison room
> On Jun 16, 2017, at 8:23 PM, Sanjoy Das <sanjoy at playingwithpointers.com> wrote:
>
> Hi Peter,
>
> On Tue, Jun 13, 2017 at 10:27 AM, Peter Lawrence via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>> Here’s what seems to really be going on
>>
>> “undef” === models an uninitialized register, but
>
> No, it specifically does
2018 May 08
0
download.file does not process gz files correctly (truncates them?)
...te problems for users and programmers who do. The current heuristic/hack
>> is in line with the compatibility approach: it detects files that are
>> obviously binary, so it changes the default behavior only for cases when it
>> would obviously cause damage.
>
> From a purely utilitarian standpoint, there are far more users who do
> not carefully read the documentation than users who do ;)
>
> (I'd also argue that basing the decision on the file extension is
> suboptimal, and it would be better to use the mime type if provided by
> the server)
Also note that MS...
2018 May 09
0
download.file does not process gz files correctly (truncates them?)
...create problems for users and programmers who do. The current heuristic/hack
>> is in line with the compatibility approach: it detects files that are
>> obviously binary, so it changes the default behavior only for cases when it
>> would obviously cause damage.
> From a purely utilitarian standpoint, there are far more users who do
> not carefully read the documentation than users who do ;)
And for that reason the behavior should be as intuitive as possible when
designed. What was intuitive 15-20 years ago may not be intuitive now,
but that should probably not be a justificatio...
2009 Jan 27
1
Asterisk & Twitter - Release/Announce only 'channel' ?
Is there a digium twitter 'user' to follow that only tweets important announcements and release information?
If there is not, I think there should be.
It would be highly utilitarian to get an SMS when there is an update to Asterisk, Dahdi, ADA etc, but I don't want to be bothered real-time with asteriskpbx tweets like: "Anyone trying anything cool with Asterisk over the weekend?".
There's nothing wrong with tweets like that, but that kind of 'incidenta...
2009 Jun 16
0
[LLVMdev] Some understanding of LLVM vs gCC vs Intel C++ Compilers
Trying to capture a notion of overall compiler optimization
in a representative set of benchmarks is a hard problem.
If you're interested in performance, it's best to measure it
on the applications you're interested in.
You should be suspicious of any one-dimensional analysis
of compiler optimization, especially if it's presented by
someone with an interest in a particular
2009 Jun 16
2
[LLVMdev] Some understanding of LLVM vs gCC vs Intel C++ Compilers
Are there any papers in the works which benchmark some specification suite
of C programs on GCC, LLVM-GCC, and CLANG?
The only stuff I have seen so far are some bar charts in a few LLVM
presentations, would be nice to have something a little more comprehensive.
Cheers,
Granville
On Tue, Jun 16, 2009 at 6:51 AM, Jon Harrop <jon at ffconsultancy.com> wrote:
> On Tuesday 16 June 2009
2004 Aug 30
2
Suitable for Dynamic IVR Platform?
New to asterisk so please be gentle. I'm guessing I'm among a number of
recent additions to the list after the article in Linux Mag. I gotta say
I'm *very* intersted in the project and will be doing lots of reading
shortly. A couble quick questions first...
How suitable is Asterisk for use as an IVR providing callers with textual
data out of a database? Can it be combined easily
2015 Jan 01
3
Design changes are done in Fedora
On Wed, December 31, 2014 12:03, Warren Young wrote:
>
> So, cope with change.
>
Is one to infer from your mantra 'cope with change' that one is not supposed
to express any opinion whatsoever, ever, on any forum; on the externalised
cost of changes made to software with no evident technical justification? And
that to do so is evidence of some moral or intellectual defect in
2018 May 03
4
download.file does not process gz files correctly (truncates them?)
Also, as mentioned in my
https://stat.ethz.ch/pipermail/r-devel/2012-August/064739.html, when
not specifying the mode argument, the default on Windows is mode = "w"
*except* for certain, case-sensitive, filename extensions:
if(missing(mode) && length(grep("\\.(gz|bz2|xz|tgz|zip|rda|RData)$", url)))
mode <- "wb"
Just like the need for mode =
2020 Jul 01
4
RFC: Adding a staging branch (temporarily) to facilitate upstreaming
On 6/30/20 2:07 PM, Chris Lattner via llvm-dev wrote:
>
>
>> On Jun 30, 2020, at 2:02 PM, Duncan Exon Smith <dexonsmith at apple.com
>> <mailto:dexonsmith at apple.com>> wrote:
>>
>>
>>
>>> On 2020-Jun-30, at 13:28, Chris Lattner via llvm-dev
>>> <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: