when I import library, conflicts shows up, is there something bad will happen?

library(tidyverse)
── Attaching packages ─────────────────────────────────── tidyverse 1.2.1 ──
:heavy_check_mark: ggplot2 3.1.0 :heavy_check_mark: purrr 0.3.0
:heavy_check_mark: tibble 1.4.2 :heavy_check_mark: dplyr 0.7.8
:heavy_check_mark: tidyr 0.8.2 :heavy_check_mark: stringr 1.3.1
:heavy_check_mark: readr 1.2.1 :heavy_check_mark: forcats 0.3.0
── Conflicts ────────────────────────────────────── tidyverse_conflicts() ──
:heavy_multiplication_x: dplyr::filter() masks stats::filter()
:heavy_multiplication_x: dplyr::lag() masks stats::lag()

This is for you to know which functions have name clashes. In general, nothing bad will happen, but if you want to be 100% certain, you can always use qualified imports in your code, e.g., stats::filter() or dplyr::filter(). This way you'll never have a problem because of conflicts like that.

2 Likes

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.

If you have a query related to it or one of the replies, start a new topic and refer back with a link.