Displaying 20 results from an estimated 900 matches similar to: "Clang project renamed"
2016 Apr 01
5
[cfe-dev] Clang project renamed
I second the motion. All in favor?
On Fri, Apr 1, 2016 at 10:57 AM, Renato Golin via cfe-dev <
cfe-dev at lists.llvm.org> wrote:
> On 1 April 2016 at 18:50, Richard Smith via cfe-dev
> <cfe-dev at lists.llvm.org> wrote:
> > * The name has been used by a kickstarter project, causing incalculable
> > confusion[0]
>
> Neal Stephenson has poetic license to do
2016 Apr 01
2
[cfe-dev] Clang project renamed
On Apr 1, 2016 5:34 PM, "George Burgess IV via cfe-dev" <
cfe-dev at lists.llvm.org> wrote:
>
> How are we casting our votes?
Discordantly!
> Will this be a standard yay-or-neigh format, or do people prefer an
alternate method?
>
> On Fri, Apr 1, 2016 at 2:27 PM, Daniel Dilts via cfe-dev <
cfe-dev at lists.llvm.org> wrote:
>>
>> I second the
2012 Mar 01
3
how to change or copy to another the names of models
Hi
I would like to know how I can change the name of a model for each
trainning cycle of a model.
I work with the RSNNS package and to build a neural network, I used :
for (i in 5:30) ....
model_ANN <- mlp(X, Y, size=n,....) # where size is the number of neurons
in the hidden layer
but I need to save each time that the model that is build (the end of each
cycle), e.g., when i = 5, I need to
2018 May 11
4
LLVM Social - Beijing: May 19th, 2018
Hi,
The first (maybe) LLVM social in Beijing will happen on May 19th, 2018.
Everyone interested in LLVM related projects is invited to join.
Event details is at https://github.com/hellollvm/website/blob/master/README.md
Presentations are welcome :-)
Looking forward to meet you !
--
Best wishes,
Wei Wu (吴伟)
2015 May 07
3
[LLVMdev] Pony Language: LLVM Project
Dear LLVM community,
I am affiliated with the design and development of the Pony<http:/www.ponylang.org> programming language, which was recently published and has since been discussed on hacker news<https://news.ycombinator.com/item?id=9482483>, reddit [1]<http://www.reddit.com/r/ponylang>
2010 Aug 22
1
fortune? (was: Re: How do you make a formal "feature" request?)
Dear all
I was wondering whether such a long post could be fortune-ed. What do you think?
Regards
Liviu
On Sat, Aug 21, 2010 at 9:33 PM, Sharpie <chuck at sharpsteen.net> wrote:
> Well, I can think of three ways it can go down:
>
>
> 1. ?You want a shiny new pony.
>
> You ask about it on the mailing list and it seems that everyone else in the
> world responds
2019 Nov 18
30
RFC: Moving toward Discord and Discourse for LLVM's discussions
Hello everyone,
*Short version:*I've set up an LLVM Discord server for real time chat
(similar to IRC) and an LLVM Discourse server for forums (similar to email
lists):
https://discord.gg/xS7Z362
https://llvm.discourse.group/
Please join and use these new services. They are only partially set up and
still very new, so don't hesitate to improve them and/or reach out to this
thread with
2019 Nov 19
3
Fwd: RFC: Moving toward Discord and Discourse for LLVM's discussions
But is it better or worse than IRC in this regard?
On Mon, Nov 18, 2019 at 10:49 PM Daniel Chapiesky via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
>
>
> ---------- Forwarded message ---------
> From: Daniel Chapiesky <dchapiesky2 at gmail.com>
> Date: Tue, Nov 19, 2019 at 1:48 AM
> Subject: Re: [llvm-dev] RFC: Moving toward Discord and Discourse for
>
2019 Nov 18
5
[cfe-dev] RFC: Moving toward Discord and Discourse for LLVM's discussions
FWIW I'm a fan of using open-source stuff for open-source projects.
Discourse looks open source, but Discord doesn't as far as I can tell (?).
On Mon, Nov 18, 2019 at 3:15 AM Chandler Carruth via cfe-dev <
cfe-dev at lists.llvm.org> wrote:
> Hello folks,
>
> I sent the message quoted below to llvm-dev@ just now, but it applies to
> the whole community so sending an FYI
2004 Oct 10
1
best params for safe archiving, 192kHz no-lax and w64 support
Hi Josh,
On Sat, 2004-10-09 at 22:41, Josh Coalson wrote:
> --- Marek Peteraj <marpet@naex.sk> wrote:
> > Hi all,
> >
> > i'd like to ask what the best options are for safe 24bit 96kHz
> > archiving. Currently i'm only using -8 but there are also some other
> > options like block size etc. Can anyone suggest?
>
> I haven't heard of
2004 Sep 17
2
Why so many lossless formats?
Hi folks,
I'm trying to get a handle on the many lossless audio formats from the
perspective of a software developer. I love the FLAC format because it is open
source and it performs very well. But there is also the MLP (Meridian
Lossless Packing), AAC (Apple Lossless), and probably some Microsoft format(s)
that compete in the same feature set. These formats all achieve
2019 Nov 18
3
RFC: Moving toward Discord and Discourse for LLVM's discussions
On Mon, 18 Nov 2019 at 07:29, Kristina Brooks via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
>
> While I understand the difficulty regarding mailing lists especially
> if one isn't used to setting up mailboxes and filters to classify and
> label emails and do think a web forum may be easier to use, I would
> have concerns over Discord. Unlike IRC which has a fairly open
2019 Nov 18
3
RFC: Moving toward Discord and Discourse for LLVM's discussions
On Mon, Nov 18, 2019 at 11:32 AM David Tellenbach via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Hi all,
>
> +1 from my side for using "faster" or "more direct" communication channels
> such
> as Discord (no strong opinion on the choice of any particular tool here)
> for
> informal chats and discussions on a "support level". This is
2019 Nov 19
2
Fwd: RFC: Moving toward Discord and Discourse for LLVM's discussions
On 11/19/19 9:09 AM, Zachary Turner via llvm-dev wrote:
Note there is also Slack, which does not have these problems. Not sure why that keeps being overlooked
My understanding is this is because Slack does not have good moderation tools. I'm unfamiliar with further details in this regard.
-Hal
On Tue, Nov 19, 2019 at 7:07 AM Zachary Turner <zturner at roblox.com<mailto:zturner at
2019 Nov 18
5
RFC: Moving toward Discord and Discourse for LLVM's discussions
The lists are working well for the people who are already invested in the
community though - as was identified by Chandler they aren't working as
well for new people.
I'm an insanely confident Scotsman with just about zero fear of any/all
social situations, and I've always found this mailing list to be utterly
terrifying (thus I've been a 10 year mostly-lurker).
My fear
2010 May 08
2
String manipulation
Dear community,
I have a problem with a string conversion:
> text
[1] "" "and" "\xc1d\xe1m"
[4] "graphical" "interface" "MLP"
[7] "Nagy" "networks" "Networks"
[10] "neural" "Neural"
2019 Nov 19
2
RFC: Moving toward Discord and Discourse for LLVM's discussions
David,
I'm glad you mentioned Discord's T&Cs. I'm not generally concerned about these kinds of things, but Discord's seems particularly aggressive. Particularly the phrase "perpetual, nonexclusive, transferable, royalty-free, sublicensable, and worldwide license" is... a lot. Since LLVM is a permissively licensed project I assume many of our contributors care about
2019 Nov 20
3
[cfe-dev] RFC: Moving toward Discord and Discourse for LLVM's discussions
On Wed, Nov 20, 2019 at 12:18 PM Renato Golin <rengolin at gmail.com> wrote:
>
> On Wed, 20 Nov 2019 at 08:44, Whisperity via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
> > There *are* open-source Discord clients, 3rd party tools and the like.
>
> This is a big uphill fight that is rarelly worthy. Not to mention
> privacy guarantees and terms and conditions
2019 Nov 18
6
RFC: Moving toward Discord and Discourse for LLVM's discussions
On Mon, Nov 18, 2019 at 11:55 AM David Chisnall via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
>
> On 18/11/2019 16:39, Stefan Teleman via llvm-dev wrote:
> > I can't recall an instance when I had difficulty using, or was
> > intimidated by, email, for saying something on a mailing list.
>
> Subscribing to a mailing list, particularly one as high-traffic as
>
2019 Nov 18
2
RFC: Moving toward Discord and Discourse for LLVM's discussions
>
> | mailing lists for longer-form discussions are unfamiliar, difficult,
> and often intimidating for newcomers
>
> Um… what? While I know (via my own children) that folks nowadays use
> multiple avenues of communication, it’s **really** hard to imagine email
> as a **mechanism** being unfamiliar/difficult/intimidating. Moving to a
> new mechanism wouldn’t alter the