memoise | Easy memoisation for R | Development Tools library

Description

This issue appears to apply to vectorised and loop approaches to renaming several files. Vectorised approach used in reprex below. The bug only seems to present when filenames do not contain meaningful or alphanumeric strings.

Summary

Existing files prior to file.rename:
"1.R" "2.R" "3.R" "4.R" "5.R".
Existing files following file.rename:
"6.R".
Expected output:
"2.R" "3.R" "4.R" "5.R" "6.R"

Reprex

I am repeatedly calling a memoised function initialised as so:

I was following along with a dynamic programming tutorial and trying to adapt their code for R. A solution I see in lots of posts for memoization in R starts by creating a local environment in which the memo object is created. That memo object doesn't get 'cleared' between calls to the function. For some common uses I could see how that would actually be a benefit-- if the calculations you're asking the function to make are basically 'fixed', then why do them multiple times in a session? But for this instance, it's a problem.

This recursive function takes a target integer and a list of integers, and returns 'TRUE' if any combination of the list (with replacement) can sum to the target, otherwise 'FALSE'.

I'm trying to install the package TStools for R. I have tried all the suggestion I've found so far through googleing, but nothing works. I get every time the same exact error:

I am working on creating a dashboard in React, and I currently have the page component holding all of the state and managing the requests to the backend api. I am considering refactoring to pull requests out of the page component - for the purpose of keeping it purely presentational - and moving all api and data logic inside the dashboard widget components.

Although I believe this is supposed to be best practice, I am concerned about certain inefficiencies. One problem I forsee is that the fetch requests will need to be memoised, otherwise some of the data shared by several of the components will be requested from the API multiple times. Another issue I forsee is that each component requires a connection to the redux state store and I am not sure of the overhead of using 'connect' versus passing the props from a useState object.

Overall, am I mostly concerned about nothing? Is this the best way to approach this? Or should I retain some logic in the page component if it reduces the number of api calls/ redux connections?

Is there a way to calculate the difference between each group efficiently? Ideally, I want to create a new column with mutate() function to show the difference (in one column, in a long format). I don't want to have to do compute the difference between each group individually.

i.e. I want to find the difference in values between each group, on a given date and hour:
arc1045 - arc1046,
arc1045 - arc1047,
arc1045 - arc1048,
arc1045 - arc1050,
arc1046 - arc1047,
arc1046 - arc1048,
.
.
.

The data frame can be retrieved using the code below.

Knitting the following Rmd file now takes ~2 minutes on a 2020 MacBook Pro:

Given a tibble that lists users, products, and product features, I am attempting to calculate the fraction of distinct product users who have a certain product feature:

I have a following function which I use to control my modals: