From: Devesh Sukhwal <bingojeeves@fastmail.com>
To: emacs-devel@gnu.org
Subject: Re: are contributions on other programming languages than C and Emacs lisp bad idea?
Date: Sat, 21 Sep 2019 08:22:04 +0530 [thread overview]
Message-ID: <EFD0CACF-833A-4CC5-BF33-0F72CF35756C@fastmail.com> (raw)
In-Reply-To: <87woe2o56x.fsf@yahoo.com.mx>
[-- Attachment #1: Type: text/plain, Size: 1493 bytes --]
Le 21 septembre 2019 06:07:10 GMT+05:30, Jorge Javier Araya Navarro <jorgejavieran@yahoo.com.mx> a écrit :
>
>
>El viernes 20 de septiembre del 2019 a las 1634 horas, Stefan Monnier
>escribió:
>
>>> Wondering this. The only downside of this would be installing more
>>> dependencies to build Emacs, say, if someone were to do a
>contribution to
>>> Emacs core with Rust
>>
>> There are two problems:
>> - imposing an additional dependency for those who compile Emacs (and
>> potentially even for those who *use* Emacs if it requires a
>specific
>> run-time library).
>> - imposing knowledge of an additional language for the maintainers.
>>
>> If the feature is *very* desirable, hard to reimplement in C or
>Elisp,
>> and is optional, I guess maybe potentially it could hypothetically
>> be discussed?
>>
>>
>> Stefan "who likes Rust, FWIW"
>
>That's what I was fearing, jaja. If a feature fulfills those three
>requirements maybe a discussion
>about it could (hypothetically) start. Got it.
>
>Was asking because I would like to run some experiments to scratch an
>itch I have, but I did not
>wanted to waste time if such thing won't be shipped with the rest of
>Emacs (or not? if anything, the
>thing I want to do can land on GNU ELPA I guess).
BTW, there is remacs ( https://github.com/remacs/remacs) for the particular itch of rust.
Thanks
--
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.
[-- Attachment #2: Type: text/html, Size: 2071 bytes --]
next prev parent reply other threads:[~2019-09-21 2:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1427040605.4453251.1569007946448.ref@mail.yahoo.com>
2019-09-20 19:32 ` are contributions on other programming languages than C and Emacs lisp bad idea? Jorge Araya Navarro
2019-09-20 21:11 ` Paul Eggert
2019-09-20 22:34 ` Stefan Monnier
2019-09-21 0:37 ` Jorge Javier Araya Navarro
2019-09-21 2:52 ` Devesh Sukhwal [this message]
2019-09-21 13:09 ` Stefan Monnier
2019-09-21 9:03 ` VanL
2019-09-21 9:46 ` Stephen Leake
2019-09-21 16:28 ` Jorge Javier Araya Navarro
2019-09-21 17:22 ` Ergus
2019-09-21 18:36 ` Eli Zaretskii
2019-09-21 21:29 ` Jorge Javier Araya Navarro
2019-09-22 15:01 ` Eli Zaretskii
2019-09-22 19:01 ` yyoncho
2019-09-22 3:51 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=EFD0CACF-833A-4CC5-BF33-0F72CF35756C@fastmail.com \
--to=bingojeeves@fastmail.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).