There is space for improvement in low level programming in Javascript,
sure isn't the main focus of the language, but I don't think
unobtrusive proposals should be a problem. There's a lot of C/C++
number apis that would be really useful in some use cases (I'm
thinking now in matrix operations,
Not sure if your failure thus far to gather what the proposal is actually
suggesting is based on your limited experimentation in using numbers in
JavaScript, or some other reason. That is ok. Your second point illustrates
the problem faced. Where your pseudo code uses String methods. That should
> What part of the proposal, in your view, did not read "it'd be nice if ..."
> number to array <--> array to number specification and standardization?
I think you missed my point in the first sentence. I'm saying the
first thing on your mind when creating proposals *shouldn't* be "it'd
be nice
>
> @guest When making a language proposal, the first thing that should be on
> your mind isn't , but the problems you're trying to solve. And these
> problems can't just be simple toy problems like a code golf challenge -
> they have to be real-world problems in code you write for sites, apps,
>
That proposal wasn't about ranges, even though it might look like it
was. It's about a special type of numeric array conversion that's
really about a particular sequence that isn't all that special in the
context of programming. [1] It also links to an SO question that
almost reads like a
@guest When making a language proposal, the first thing that should be
on your mind isn't "it'd be nice if ...", but the problems you're
trying to solve. And these problems can't just be simple toy problems
like a code golf challenge - they have to be real-world problems in
code you write for
There is already a very well thought out list, although to my knowledge it
has never been officially blessed, at https://esdiscuss.org/topic/ranges.
Quoting:
It seems odd that after all these years of discussions and meta-discussions
about ES feature proposals, some people are still saying
Am not concerned with "down" votes. Do not really care about "up" or "down"
votes. Would only object directly to *censorship, *which unfortunately, is
practiced from top-down (CEO; management; moderators; "trusted users";
etc.) at the linked sites. That is beyond the scope of this proposal.
Cannot get into "a large number of users" heads. Again, am not interested
in overcoming conjecture. If the proposal does not meet you folks'
criteria, so be it.
On Thu, Mar 7, 2019 at 10:46 PM Steve Fink wrote:
> Any addition to the JavaScript language needs to (1) be motivated by a use
> case
It's entirely possible that I'm being thick here, but can you expand on the
use case?
- The initial link that you posted results in a code challenge that was
voted down to a negative score as a result of ambiguity in the challenge
description, and...
- the two expressions you provided
Have you read the proposal, and the first response to your inquiry? It is
simpler to have the ability to add, subtract, divide, or otherwise
manipulate individual nth indexes of an integer or decimal represented as
an array of integers potentially containing one decimal than trying to
perform the
By "real world" we mean somewhere outside of a code challenge or similarly
low utility program context.
You mentioned statistics, for example. Can you reference a specific example
from that domain where these methods would offer an advantage?
On Thu, Mar 7, 2019, 5:05 PM guest271314 wrote:
>
Not sure what you mean by "real world" use case. Described at least one use
case at the proposal. Statistics; graphs; number and integer manipulation
using indexes of arrays with ability to convert manipulated array back to
number.
On Thu, Mar 7, 2019 at 9:56 PM Naveen Chawla wrote:
> What is
What is the real world use case, presuming it's not just an academic
exercise
On Thu, 7 Mar 2019, 9:08 pm guest271314, wrote:
> Ability to adjust *nth* digit of an integer or decimal by adjusting
> decimal or integer at *nth* index of array, to try to solve OEIS A217626
> oeis.org/A217626
The original motivation was trying to solve OEIS A217626 directly, that is,
without generating all of the permutations, specifically, using only a
multiple of 9 directly. See proposal at
> Ability to adjust *nth* digit of an integer or decimal by adjusting
> decimal or integer at *nth* index of
15 matches
Mail list logo
