Skip to main content
9 events
when toggle format what by license comment
Jan 11, 2021 at 22:09 comment added J. Mini R's bad error messages need to be seen to be believed. You might want to add an example of just how bad it gets. You'll get an error about something called dim(X) and not be told what line triggered it, what X is, or which function in your code called dim.
Jan 11, 2021 at 19:52 comment added Andreas Dzemski @SextusEmpiricus Yes, exactly. Trips me up almost every time I refactor code. I guess it would maybe suffice to have a linter that complains about references to variables that are not defined within a function. Maybe something like that already exists?
Jan 11, 2021 at 15:55 comment added Sextus Empiricus Do you mean that test = function() {return(pi)} will return whatever value pi has in the global environment and it should be instead explicitly defined inside the function or otherwise an error should be returned?
Jan 11, 2021 at 15:12 comment added Andreas Dzemski @SextusEmpiricus re scoping issues. maybe there is a better word for the problem I am describing?
Jan 11, 2021 at 15:11 comment added Andreas Dzemski @SextusEmpiricus re error messsages. I've deleted the speculation about why this may be difficult to address. Maybe this can be addressed within the current framework. E.g., the error messages within the tidyverse are a lot better than base R errors.
Jan 11, 2021 at 15:09 history edited Andreas Dzemski CC BY-SA 4.0
deleted 145 characters in body
Jan 11, 2021 at 14:39 comment added Sextus Empiricus Could you add references about two points (the fundamental decisions that make error messages less useful and the scoping issues). To me these are new.
S Jan 11, 2021 at 14:32 history answered Andreas Dzemski CC BY-SA 4.0
S Jan 11, 2021 at 14:32 history made wiki Post Made Community Wiki by Andreas Dzemski