Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

koperagen
Copy link
Collaborator

Review commits one by one, they are not related to each other
Note that i provided explanations b154937 in commit message
Here you can find how to enable fir dump for an individual test
plugins/kotlin-dataframe/testData/box/propertiesOrder.kt

Dumps change after updating the compiler, or when the library changes, and it leads to conflicts. It would be better to add more "checks" in the test code itself, and only opt in FIR_DUMP directive for individual tests when needed
@koperagen koperagen self-assigned this Jun 26, 2024
Copy link
Collaborator

@Jolanrensen Jolanrensen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just some small things :)

FILE: read.kt
package org.jetbrains.kotlinx.dataframe

FILE: propertiesOrder.kt
public final fun box(): R|kotlin/String| {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You wanted to exclude these files right?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I opt in fir dump for this file specifically. Would be good to have a few of them present to track changes in generated code, like for example there's this @Order annotation and IDE plugin relies on it

@@ -28,9 +28,8 @@ FILE: selectDuringTyping.kt
}

local abstract class ExplodeSchema_94 : R|<local>/ExplodeSchema_94I| {
public abstract var scope0: R|<local>/Scope0|
@R|org/jetbrains/kotlinx/dataframe/annotations/ScopeProperty|() public abstract val scope0: R|<local>/Scope0|
public get(): R|<local>/Scope0|
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should the fir files in diagnostics also be included, or are they fine?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For diagnostics tests, FIR dumps are needed to verify that warnings/errors were actually reported, it seems

* This annotation serves to distinguish between the two where needed
*/
@Target(AnnotationTarget.PROPERTY)
public annotation class ScopeProperty
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do you use this annotation already somewhere? I'm curious to see how/where it's used :)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you mean by use? :o
Here generated property is annotated
plugins/kotlin-dataframe/src/org/jetbrains/kotlinx/dataframe/plugin/extensions/TokenGenerator.kt

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Plus other things from the same commit

Copy link
Collaborator

@Jolanrensen Jolanrensen Jun 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ooh so this annotation class is only used on generated properties. That wasn't clear to me

Copy link
Contributor

Generated sources will be updated after merging this PR.
Please inspect the changes in here.

@koperagen koperagen merged commit 78795e5 into master Jun 27, 2024
@Jolanrensen Jolanrensen added the Compiler plugin Anything related to the DataFrame Compiler Plugin label Aug 8, 2024
@koperagen koperagen deleted the col-kinds branch August 26, 2024 13:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Compiler plugin Anything related to the DataFrame Compiler Plugin
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants